Exchange item group sharing in a computing network

ABSTRACT

A method includes obtaining, by a first computing device, a digital exchange item. The method further includes sending, to a server, a request to share the digital exchange item with a group of computing devices. The method further includes determining, by the server, whether the digital exchange item can be shared based on one or more of: an issuer agreement and exchange item rules. When the digital exchange item can be shared, the method further includes the server establishing secure custody rights for each computing device, determining haring rights regarding the digital exchange item, and generating replications of the digital exchange item. The method further includes the server uploading the replications and the sharing rights to digital wallets associated with the computing devices of the group.

CROSS REFERENCE TO RELATED PATENTS

The present U.S. Utility Patent Application claims priority pursuant to 35 U.S.C. §119(e) to U.S. Provisional Application No. 62/370,345, entitled “CROSS-BRAND REDEMPTION IN AN EXCHANGE ITEM MARKETPLACE NETWORK”, filed Aug. 3, 2016, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not Applicable

INCORPORATION-BY-REFERENCE OF MATERIAL SUBMITTED ON A COMPACT DISC

Not Applicable

BACKGROUND OF THE INVENTION Technical Field of the Invention

This invention relates generally to computer networks and more particularly to an exchange item marketplace network.

Description of Related Art

The use of credit cards, debit cards, and gift cards to pay for goods and services is well known. It is further known to use services such as PayPal™ or Apple Pay™ to expand the use of credit cards and debit cards through computing devices (e.g., computers, tablets, cell phones, etc.). The use of these services is aided by the standardized numbering system and format used by credit card issuers and debit card issuers.

For a credit card and debit card transaction, the credit or debit cardholder presents the credit or debit card to a merchant (e.g., on line or brick & mortar) to pay for a purchase. The merchant uses point of sale (POS) equipment to capture the information of the credit or debit card and to enter the amount of the purchase. This information is sent to an acquirer (e.g., the financial institution of the merchant). The acquirer sends the transaction information via a secure network of a credit card company to the cardholder's issuer (e.g., a financial institution that issued the credit or debit card to the cardholder).

The issuer approves or declines the transaction and sends the response back to the acquirer via the secure network of the credit card company. The acquirer sends the response (e.g., approved or declined) to the merchant to complete the transaction. Money, however, is not exchanged at the time of purchase, but is done during clearing and settlement.

Clearing and settlement begins when the merchant deposits the transaction receipt with the acquirer. The acquirer credits the merchant's account and sends the transaction receipt to the issuer via the secure network. The issuer posts the transaction to the cardholder's account. The cardholder pays the issuer in response to receiving a monthly statement.

The issuance and use of a gift card is significantly different than that of a credit card. A branded company (e.g., a retailer, a chain store, a restaurant, etc.) issues a request to create gift cards to a processor service. The processor service creates the gift cards, which may be issued with specific values or issued as blanks; where the value is specified at the time of purchase.

The processor service provides the gift cards to a distributor who is responsible for distributing the gift cards so that a consumer may purchase them. For example, the distributor may provide gift cards to merchants so they may sell the gift cards. At some point, a consumer purchases a gift card (e.g., a sporting goods company gift card for $50.00). The payment for the gift card is processed such that the distributor, processing service, and branded company each are paid their respective shares.

If the gift card is used, a merchant (e.g., a franchise owner of the branded company) captures information of the gift card via point of sale (POS) equipment. The information of the gift card is processed to determine if it is a valid gift card and to determine the balance remaining on the gift card. If the card is valid, the use of the gift card is authorized up to the balance remaining on the gift card. Once the use is complete, the balance is updated, processing fees are paid, and the branded company is debited.

Another difference between credit cards and gift cards is that gift cards do not have a standardized numbering system or format. As such, gift cards can have one of thousands of different numbering systems and formats, which have to be recognizable by the POS equipment.

Yet another difference between credit cards and gift cards is when money is processed. For credit cards, money is not processed until a purchase occurs, while gift cards are purchased and then subsequently used. As such, money is processed at the time of purchase of the gift card and again if the gift card is used.

A still further difference between credit cards and purchased gift cards is that, if a credit card goes unused, no money is spent. In contrast, if a purchased gift card goes unused, money has been spent to acquire the card, but no goods or services are acquired. It is estimated that billions of dollars' worth of purchased gift cards go unused annually. While this may be a favorable scenario for the branded company, it is not a favorable scenario for consumers.

Raise Marketplace Inc. introduced a system that enables gift cardholders to sell their unused or unwanted gift cards. This system allows a gift card seller to post a gift card for sale in a virtual gift card marketplace. Buyers can access the virtual gift card marketplace and purchase gift cards that are offered for sale. When a gift card is purchased, the system processes the purchase to debit the buyer, credit the seller, and provide the gift card to the buyer.

The system may provide the physical gift card to the buyer, which requires obtaining the physical gift card from the seller and delivering it to the buyer. Alternatively, the system provides the information of the gift card to the user in a voucher format (e.g., a document that the buyer can print off that includes the relevant information of the gift card).

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

FIG. 1 is a schematic block diagram of an embodiment of an exchange item marketplace network in accordance with the present invention;

FIG. 2 is a schematic block diagram of an embodiment of user device of exchange item marketplace network in accordance with the present invention;

FIG. 3 is a schematic block diagram of an embodiment of a marketplace server of exchange item marketplace network in accordance with the present invention;

FIG. 4 is a schematic block diagram of another embodiment of an exchange item marketplace network in accordance with the present invention;

FIG. 5 is a schematic block diagram of another embodiment of an exchange item marketplace network in accordance with the present invention;

FIG. 6 is a schematic block diagram of another embodiment of an exchange item marketplace network in accordance with the present invention;

FIG. 7A is a schematic block diagram of another embodiment of an exchange item marketplace network in accordance with the present invention;

FIG. 7B is a schematic block diagram of a transactions blockchain in accordance with the present invention;

FIG. 7C is another schematic block diagram of a transactions blockchain in accordance with the present invention;

FIG. 7D is a logic diagram of an embodiment of a method for generating a transactions blockchain in accordance with the present invention;

FIG. 7E is a logic diagram of another embodiment of a method for generating a transactions blockchain in accordance with the present invention;

FIG. 8A is a logic diagram of an embodiment of a method for utilizing an exchange item in an exchange item marketplace network in accordance with the present invention;

FIG. 8B is a logic diagram of an embodiment of a method for utilizing rules in an exchange item marketplace network in accordance with the present invention;

FIG. 8D is a schematic block diagram of another embodiment of an exchange item marketplace network in accordance with the present invention;

FIG. 8E is a schematic block diagram of another embodiment of an exchange item marketplace network in accordance with the present invention;

FIG. 8F is a schematic block diagram of another embodiment of an exchange item marketplace network in accordance with the present invention;

FIG. 8G is a schematic block diagram of another embodiment of an exchange item marketplace network in accordance with the present invention;

FIG. 8H is a diagram of an exchange item database in accordance with the present invention;

FIG. 8J is another schematic block diagram of a transactions blockchain in accordance with the present invention;

FIG. 8K is a logic diagram of an embodiment of a method for modifying an exchange item in an exchange item marketplace network in accordance with the present invention;

FIG. 8L is a schematic block diagram of another embodiment of an exchange item marketplace network in accordance with the present invention;

FIG. 8M is a logic diagram of an embodiment of a method for securely modifying an exchange item in an exchange item marketplace network in accordance with the present invention;

FIG. 8N is a schematic block diagram of another embodiment of an exchange item marketplace network in accordance with the present invention;

FIG. 8P is a logic diagram of an embodiment of a method for securely processing an exchange item in an exchange item marketplace network in accordance with the present invention;

FIGS. 9A and 9B are schematic block diagrams of another embodiment of an exchange item marketplace network in accordance with the present invention;

FIG. 9C is a logic diagram of an embodiment of a method for redeeming a cross-brand exchange item in an exchange item marketplace network in accordance with the present invention;

FIG. 10A is a schematic block diagram of another embodiment of an exchange item marketplace network in accordance with the present invention;

FIG. 10B is a logic diagram of an embodiment of a method for anonymous acquisition of an exchange item in an exchange item marketplace network in accordance with the present invention;

FIG. 11A is a schematic block diagram of another embodiment of an exchange item marketplace network in accordance with the present invention;

FIG. 11B is a logic diagram of an embodiment of a method for identifying unauthorized exchange item cloning in an exchange item marketplace network in accordance with the present invention;

FIG. 12A is a schematic block diagram of another embodiment of an exchange item marketplace network in accordance with the present invention;

FIG. 12B is a logic diagram of an embodiment of a method for modifying brand affiliation of an exchange item in an exchange item marketplace network in accordance with the present invention;

FIG. 13A is a schematic block diagram of another embodiment of an exchange item marketplace network in accordance with the present invention;

FIG. 13B is a logic diagram of an embodiment of a method for offering an exchange item in response to a use pattern in an exchange item marketplace network in accordance with the present invention;

FIGS. 14A and 14B are schematic block diagrams of another embodiment of an exchange item marketplace network in accordance with the present invention;

FIG. 14C is a schematic block diagram of an embodiment of a use processing in accordance with the present invention;

FIG. 14D is a logic diagram of an embodiment of a method for authorizing exchange item redemption in an exchange item marketplace network in accordance with the present invention;

FIG. 15A is a schematic block diagram of another embodiment of an exchange item marketplace network in accordance with the present invention;

FIG. 15B is a logic diagram of an embodiment of a method for replacing a fraudulently obtained exchange item in an exchange item marketplace network in accordance with the present invention;

FIG. 16A is a schematic block diagram of another embodiment of an exchange item marketplace network in accordance with the present invention;

FIG. 16B is a logic diagram of an embodiment of a method for establishing a fraud status for an account in an exchange item marketplace network in accordance with the present invention;

FIG. 17A is a schematic block diagram of another embodiment of an exchange item marketplace network in accordance with the present invention;

FIG. 17B is a logic diagram of an embodiment of a method for facilitating restitution for unfavorable exchange item redemption in an exchange item marketplace network in accordance with the present invention;

FIG. 18A is a schematic block diagram of another embodiment of an exchange item marketplace network in accordance with the present invention;

FIG. 18B is a logic diagram of an embodiment of a method for redistributing an exchange item in an exchange item marketplace network in accordance with the present invention;

FIG. 19 is a schematic block diagram of another embodiment of an exchange item marketplace network in which computing devices are sharing an exchange item in accordance with the present invention;

FIG. 20 is a logic diagram of a method of computing devices sharing an exchange item in accordance with the present invention;

FIG. 21 is a logic diagram of a further method of computing devices sharing an exchange item in accordance with the present invention;

FIG. 22 is a logic diagram of a further method of computing devices sharing an exchange item in accordance with the present invention;

FIGS. 23A and 23B are an example of computing devices sharing an exchange item in accordance with the present invention;

FIG. 24 is another example of computing devices sharing an exchange item in accordance with the present invention;

FIG. 25 is an example of a secure data block in accordance with the present invention; and

FIGS. 26A and 26B are another example of a secure data block in accordance with the present invention.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 is a schematic block diagram of an embodiment of an exchange item marketplace network 10 that includes user devices 12 of individual sellers, user devices 14 of bulk sellers, user devices 16 of individual buyers, one or more marketplace servers 18 (an example embodiment is shown in FIG. 3), one or more databases 20, one or more networks 24, one or more brand server(s) 26, one or more processor servers 28, one or more distributor servers 30, point of sale (POS) equipment 32, and one or more retailer servers 34. Hereafter, the exchange item marketplace network 10 may be interchangeably referred to as a marketplace network, a system, a communication system, a data communication system, a computing network, a computing system, and/or a communication network. The one or more marketplace servers 18 process, and the one or more databases 20 store a virtual marketplace of exchange items 22. Hereafter, the virtual marketplace of exchange items 22 may be interchangeably referred to as a virtual marketplace, a marketplace, and exchange items.

Each of the user devices 12, 14, and 16 is a computing device that includes a computing core. In general, a computing device is any electronic device that can communicate data, process data, and/or store data. A further generality of a computing device is that it includes a central processing unit (CPU), a memory system, user input/output interfaces, peripheral device interfaces, and an interconnecting bus structure.

As specific examples, each of the user devices 12-16 may be a portable computing device and/or a fixed computing device. A portable computing device may be a social networking device, a gaming device, a cell phone, a smart phone, a personal digital assistant, a digital music player, a digital video player, a laptop computer, a handheld computer, a tablet, a video game controller, and/or any other portable device that includes a computing core. A fixed computing device may be a personal computer (PC), a computer server, a cable set-top box, a satellite receiver, a television set, a printer, a fax machine, home entertainment equipment, a video game console, and/or any type of home or office computing equipment that includes a computing core. An embodiment of a computing device 12-16 is further described below with reference to FIG. 2.

The exchange item marketplace network 10 supports the selling and purchasing of exchange items. An exchange item is a closed loop financial instrument and/or other digital goods. For example, a closed loop financial instrument is a gift card, a voucher, a store credit, and/or other brand company (or merchant) sponsored form of credit for a specific use (e.g., in a specific store, in a specific chain of stores, for a particular type of goods, etc.). A closed loop financial instrument is distinguished from an open loop financial instrument, such as a credit card.

A digital good is a digital item that can legally be sold or resold by an individual. For example, the digital item may be an original digital book, an original digital photograph, an original video clip, a purchased video game, a purchased software application, a purchase video, a purchased music file, a purchased digital book, a purchased audio book, etc.

In support of selling an exchange item, the marketplace server 18 communicates with a user device of a seller (e.g., individual or bulk) to verify the user device (and the seller) and to ascertain information regarding the exchange item being offered for sale. For example, the marketplace server 18 verifies user information (e.g., the seller's name, account, personal identification number (PIN), a user identification number (ID), payment account information (e.g., a credit card number, checking or savings account information), seller's mailing address, etc.) and device information (e.g., an IP address, device serial number, a marketplace application ID, etc.) of the seller's computing device. Verification of the seller and corresponding computing device is discussed in greater detail with reference to FIG. 6A.

Upon receiving the information regarding the exchange item, which includes a brand name (e.g., a coffee franchise, a sporting good franchise, an electronics store, etc.), a serial number, a selling price, a remaining balance, restrictions of use, a bar code, and/or other pertinent information, the marketplace server 18 verifies it. When the seller and the information regarding the exchange item are verified, the marketplace server 18 posts it in the virtual marketplace of exchange items 22, which is stored in database 20.

The marketplace server 18 posts the exchange item in the virtual marketplace 22 by creating a digital representation of the exchange item. To do this, the server creates a digital image of the exchange item, determines the brand of the exchange item, and the information regarding the exchange item (e.g., a brief description, brand, selling price, balance, serial number, restrictions (if any), expiration date (if any), and/or any other pertinent information). In accordance with an organization protocol of the virtual marketplace, the digital representation of the exchange item is added. For instance, the organization protocol groups exchange items by types (e.g., restaurants, sporting goods, coffee shops, automotive goods, etc.), by brands (e.g., a sporting goods chain, a coffee shop chain, etc.), by sales price, by balance of the exchange item, by a savings value (e.g., a difference between the balance and the sales price), by expiration date, by date offered for sale, by special promotions, by seller, by restrictions, by a brief description (e.g., title of a video for resale), and/or any other organization scheme that lends itself to searching for particular items.

As such, for a particular exchange item offered for sale, its digital representation is added to the database 20 and will be displayed within a grouping per the organization protocol when a potential buyer or other user of the system 10 selects the grouping. In one example, if the exchange item is a gift card, a digital image of the gift card is displayed along with at least some of the related information (e.g., sales price, balance, etc.). If the gift card includes a logo of the branded company offering the gift card, the logo is often displayed in accordance with requirements of the branded company.

A potential buyer of an exchange item offered for sale accesses the system 10 using its user device 16. For example, the user device 16 logs into the system 10. If the user device 16 is associated with a buyer that does not have an account with the system 10, the buyer creates one through the user device 16 with the system. For buyers with an account, the marketplace server 18 verifies the buyer user device 16 before allowing it access to the virtual marketplace 22. The buyer verification process is discussed in greater detail with reference to FIG. 4.

Once the buyer is verified, the buyer computing device 16 is allowed access the virtual marketplace 22. The buyer computing device 16 uses searching criteria that are in accordance with the organization protocol to search the virtual marketplace 22 for exchange items of interest. The marketplace server 18 provides video-graphics data to the buyer computing device 16 in accordance with the searching. When the buyer computing device 16 finds exchange items of interest, it displays the video-graphics of the corresponding exchange items (e.g., a grouping of gift cards).

The buyer computing device 16 receives an input corresponding to a selection of one of the exchange items of interest for purchase. The buyer computing device 16 sends the selected exchange item to the marketplace server 18 for processing.

The marketplace server 18 processes the selected exchange item via a multiple step process. One step includes verifying that the buyer is authorized to purchase the exchange item (e.g., has the financial resources, is not limited by buying restrictions (e.g., dollar amount, quantity, type, etc.), is a legitimate buyer, etc.). Another step includes verifying integrity of the information of the selected exchange item (e.g., balance remaining is accurate, the offer to sell the exchange item has not been withdrawn, the exchange item is not currently being processed for sale to another buyer, the exchange item is not expired, the exchange item has not been voided by the branded company, etc.).

When the buyer is authorized and the information regarding the selected exchange item has been verified, another step includes removing the exchange item from the virtual marketplace 22. Another step includes processing payment for the selected exchange item. The multiple step buying process is further described with reference to FIG. 4.

FIG. 2 is a schematic block diagram of an embodiment of computing device 12-16 of exchange item marketplace network 10. The computing device 12-16 includes a computing core 52, one or more input devices 54 (e.g., keypad, keyboard, touchscreen, voice to text, etc.), one or more audio output devices 56 (e.g., speaker(s), headphone jack, etc.), one or more visual output devices 58 (e.g., video graphics display, touchscreen, etc.), one or more universal serial bus (USB) devices, one or more networking devices (e.g., a wireless local area network (WLAN) device 84, a wired LAN device 86, a wireless wide area network (WWAN) device 88 (e.g., a cellular telephone transceiver, a wireless data network transceiver, etc.), and/or a wired WAN device 90), one or more memory devices (e.g., a flash memory device 92, one or more hard drives 94, one or more solid state (SS) memory devices 96, and/or cloud memory 98), and one or more peripheral devices.

The computing core 52 includes a video graphics processing unit 60, one or more processing modules 62, a memory controller 64, main memory 66 (e.g., RAM), one or more input/output (I/O) device interface module 68, an input/output (I/O) interface 70, an input/output (I/O) controller 72, a peripheral interface 74, one or more USB interface modules 76, one or more network interface modules 78, one or more memory interface modules 80, and/or one or more peripheral device interface modules 82. Each of the interface modules 68, 76, 78, 80, and 82 includes a combination of hardware (e.g., connectors, wiring, etc.) and operational instructions stored on memory (e.g., driver software) that is executed by the processing module 62 and/or a processing circuit within the interface module. Each of the interface modules couples to one or more components of the computing device 12-16. For example, one of the JO device interface modules 68 couples to an audio output device 56. As another example, one of the memory interface modules 80 couples to flash memory 92 and another one of the memory interface modules 80 couples to cloud memory 98 (e.g., an on-line storage system and/or on-line backup system).

FIG. 3 is a schematic block diagram of an embodiment of a marketplace server 18 of exchange item marketplace network 10. The server 18 includes a computing core 122, one or more input devices 54 (e.g., keypad, keyboard, touchscreen, voice to text, etc.), one or more audio output devices 56 (e.g., speaker(s), headphone jack, etc.), one or more visual output devices 58 (e.g., video graphics display, touchscreen, etc.), one or more networking devices (e.g., a wireless local area network (WLAN) device 84, a wired LAN device 86, a wireless wide area network (WWAN) device 88 (e.g., a cellular telephone transceiver, a wireless data network transceiver, etc.), and/or a wired WAN device 90), one or more memory devices (e.g., a flash memory device 92, one or more hard drives 94, one or more solid state (SS) memory devices 96, and/or cloud memory 98), and one or more peripheral devices. Note that the server 18 may include more or less devices than shown in this example embodiment of a server.

The computing core 122 includes a video graphics processing unit 60, a plurality of processing modules 62, a memory controller 64, a plurality of main memories 66 (e.g., RAM), one or more input/output (I/O) device interface module 68, an input/output (I/O) interface 70, an input/output (I/O) controller 72, a peripheral interface 74, one or more network interface modules 78, and/or one or more memory interface module 80.

FIG. 4 is a schematic block diagram of another embodiment of an exchange item (EI) marketplace (MP) network that includes the seller's computing device 12, the buyer's computing device 16, a seller's financial server 190, a service provider's financial server 192, a buyer's financial server 194, the marketplace (MP) server(s) 18, and the database 20, which includes the virtual marketplace of exchange items 22. Each of the seller's computing device 12 and buyer's computing device 16 includes a marketplace interface 142, which includes a web browser 196 and a mobile application 198.

The MP server 18 performs function blocks that includes a seller verification 200, a deny 202, an exchange item verification 204, an add exchange item to marketplace 206, a buyer verification 208, a deny 210, an exchange item purchase verification 212, an exchange item payment processing 214, a remove exchange item from marketplace 216, an add exchange item to buyer's wallet 218, an exchange item use 220, and an exchange item balance update 222.

As an example of operation, the mobile application 198 of the seller's computing device 12 sends a request to sell an exchange item to the marketplace (MP) server(s) 18. The server 18 performs the seller verification 200 functional block to determine whether the seller and/or the seller's computing device 12 are a valid seller (e.g., device and/or seller are valid). When invalid, the server(s) 18 performs the deny 202 functional block to communicate a denial of the request to sell the exchange item to the seller's computing device 12.

When the seller is verified, the server performs the exchange item verification 204 functional block to determine whether the exchange item is valid (e.g., is a valid exchange item, perform a balance check with an associated entity, i.e., a retailer, etc.). When invalid, the server(s) perform the deny 202 functional block. When the exchange item is valid, the server(s) 18 perform the add exchange item to marketplace 206 functional block to add a digital representation of the exchange item to the virtual marketplace of exchange items 22 (e.g., creates a new entry for inventory within the virtual marketplace of exchange items 22).

When a buyer desires to purchase an exchange item, the mobile application 198 of the buyer's computing device 16 sends a request to buy a selected exchange item to the MP server(s) 18. The server(s) 18 perform the buyer verification 208 functional block to determine whether the buyer is valid (e.g., the user and/or buyer computing device are valid). When invalid, the server(s) 18 perform the deny 210 functional block to issue a denial of the purchase request to the buyer's computing device 16.

When the buyer is validated, the server(s) 18 perform the exchange item purchase verification 212 functional block to verify that the buyer, via the buyer's computing device, has sufficient means (e.g., money, credit, valid credit card, valid debit card, etc.) to pay for the selected exchange item. For example, the exchange item purchase verification 212 functional block enables the server 18 to receive buyer information from the buyer's financial server 194 verifying payment and/or verifying an ability to pay. When unable to purchase the selected exchange item, the server 18 performs the deny 210 functional block.

When the buyer is able to purchase the selected exchange item, the server 18 performs the exchange item payment processing 214 functional block to process payment for the selected exchange item. For example, the server 18 collects payment from the buyer's e-wallet, the buyer's computing device 16, or the buyer's financial server 194, issues a payment to the seller's e-wallet, to the seller's computing device, or to the seller's financial server 190, and issues a commission payment to the service provider's financial server 192.

After processing payment or concurrent with the processing of the payment, the server 18 performs the remove exchange item from marketplace 216 functional block to remove the selected exchange item from the virtual marketplace of exchange items 22. For example, the server 18 deletes an entry associated with the selected exchange item from the database 20.

The server 18 performs the add exchange item to the buyer's wallet 218 functional block to facilitate adding the exchange item to a buyer's e-wallet. For example, the server 18 updates a representation of the buyer's wallet within the database 20 to include a digital representation of the purchased exchange item and issues a message to the mobile application 198 to store a local copy of the digital representation within the buyer's computing device 16.

When the buyer desires to purchase something using an exchange item, the mobile application 198 communicates a utilization message to the server 18. The server 18 evokes the exchange item use 220 functional block to receive the utilization message and to facilitate communication with other servers for verification and transaction execution. For example, the server 18 forwards the utilization message to a retailer server associated with the exchange item to initiate execution of the transaction. Having successfully used the exchange item, the server 18, via the exchange item balance update 222 functional block, updates the buyer's wallet to indicate that the exchange item has been utilized and to update the balance remaining on the exchange item, when appropriate.

FIG. 5 is a schematic block diagram of another embodiment of an exchange item marketplace network 10A that includes a plurality of sellers 702, a plurality of buyers 704, and an on-line exchange item marketplace 700. Hereafter, the exchange item marketplace network 10A may be interchangeably referred to as a system, a communication system, and a communication network. The sellers 702 include individual sellers 706, bulk resellers 708, and retailers 710. The buyers 704 include individual buyers 712 and other types of buyers 714 (e.g., bulk buyers, resale buyers, etc.).

Each seller 702 and each buyer 704 corresponds to a computing device 12-16 that includes a marketplace interface module 716 that enables the computing device access to the marketplace 700 and to function therein. The marketplace interface module 716 includes a browser application 722, a mobile device application 720, and/or any type of application that enables access to the marketplace 700. The computing core 52 of the user device executes one or more of these applications. For instance, each of the applications includes operational instructions that are stored in memory (e.g., main memory, flash memory, SS memory, HD memory, and/or cloud memory) and executed by the processing module 62 of the computing core 52.

Alternatively, the marketplace interface module 716 includes a processing circuit and memory, wherein the memory stores and the processing circuit executes the operational instructions of the application. As yet another alternative, the processing circuit of the marketplace interface module 716 and the processing module 62 of the computing core 52 co-process the operational instructions of one or more of the applications. Interface 718 functions in a similar manner to provide bulk resellers 708 and/or retailers 710 access and function within the marketplace 700.

One or more marketplace servers 18 supports the on-line exchange item (EI) marketplace 700 by performing the functions of the corresponding functional blocks. The functional blocks include seller software tools 738, individual seller fraud detection 724, individual sale processing 726, bulk seller verification processing 730, bulk sale processing 732, retailer verification processing 734, retailer sale processing 736, displaying exchange items for sale 728 in the marketplace 700, payment processing 748, MP user e-wallet 750, buyer fraud detection 740, purchase processing 742, consumer profiles 744, and market customization 746. A functional block includes one or more of a standalone processing module that executes operational instructions to perform the corresponding functions of the block, a software algorithm executed by the computer core of the server to perform the corresponding functions of the block, and/or a combination thereof.

The server(s) 18 perform the marketplace user e-wallet functional block 750 to create and maintain an e-wallet for a user of the marketplace 700. The e-wallet is essentially a file for an individual user (e.g., a person, a legal entity, etc.) that stores information regarding exchange items bought, sold, and/or used by the user. For example, the e-wallet stores a digital representation of each purchased exchange item that has a value greater than zero. For example, a digital representation of a gift card is displayed in an asset section of the e-wallet while the gift card has a balance above zero and the gift card has not expired. When the balance is zero or the gift card expires, the digital representation is removed and the information regarding the gift card is stored in an archive section of the e-wallet.

The e-wallet is further capable of storing and tracking marketplace credit. For example, a user may purchase marketplace credit that is subsequently used to purchase an exchange item. In addition, a seller of an exchange item may be paid in marketplace credit that the seller may use to purchase an exchange item or cash out.

The e-wallet further functions to archive data regarding previous exchange item purchases and/or previous exchange item sales. The amount of data stored for each exchange item purchase or sale may be user defined or set based on a system default setting. For example, the data for a purchase includes one or more of a purchase price, the exchange item ID, a serial number, a brand name, a purchase date, the value of the exchange item, restrictions of the exchange item, and an expiration date. The data for a purchased exchange item may further include use information (e.g., when the exchanged item was used, the amount of value used, the date of use, the place of use, etc.) and/or remaining value information.

As another example, the data for a sale includes one or more of an asking selling price, a sold price, the exchange item ID, a serial number, a brand name, an offer for sale time stamp, a sold time stamp, the value of the exchange item, restrictions of the exchange item, and an expiration date. The data for a sold exchange item may further include price reduction information (e.g., the amount of the change, a change time stamp, etc.) and/or information regarding a withdrawal of an offer for sale.

The server(s) 18 perform the seller software tools functional block 738 to assist a seller (e.g., individual, bulk, or retailer) in setting a price for an exchange item. For example, the server(s) 18 record data regarding exchange items offered for sale, data regarding purchases of exchange items, and data regarding exchange items for which the offer for sale was withdrawn. From this data, the server(s) 18 determines predictive sales information. For example, the server(s) 18 determines for a particular type of exchange item (e.g., a gift card for a particular franchise) a correlation between the value of the exchange item and duration in the marketplace (e.g., a $250 gift card has an average duration of 1 day, a $100 gift card has an average duration of 12 hours, a $50 gift card has an average duration of 5 hours, etc.).

As another example of predictive sales information, the server(s) 18 determine a correlation between sales price and duration in the marketplace (e.g., a 5% discount has an average duration of 12.5 hours, a 3% discount has an average of 1 day, and a 10% discount has an average duration of 1.5 hours). As yet another example, the server(s) 18 determine a periodic sales volume for a particular exchange item (e.g., how many sold in an hour, six hours, a day, etc.). As yet another example, the server(s) 18 determine a current quantity of the particular exchange items for sale (e.g., how many are currently being offered for sale, at what sales price, the current average duration in the marketplace, etc.). The server(s) 18 may further analyze any type of data maintained by the system 10A to assist in the creation of predictive sales information.

In addition to creating the predictive sales information, the server(s) 18 generate a seller's profile, which includes information regarding the sales tendencies and/or preferences of a particular seller. For example, the seller's profile includes information regarding one or more of the types of exchange items offered for sale, information regarding if and when exchange item offers for sale are withdrawn, initial asking prices for exchange items offered for sale, actual sales price information and corresponding discounted percentage, frequency for which initial asking price is adjusted, average duration of exchange items in the marketplace, standard deviation of duration of exchange items in the marketplace, etc.

From the predictive sales information and the seller's profile, the server(s) 18 provide a suggested sales price for a particular exchange item. For example, the seller profile indicates that the seller has a tendency to offer a particular exchange item with a minimal discount and prefers that the exchange item remain in the marketplace for less than 6 hours. Further, the predictive sales information for the particular exchange item indicates that there is currently above normal quantity of the exchange item for sale, the current asking price has a greater discount than the seller's preference, and the current average duration in the marketplace is 7 hours, the server(s) 18 provides one or more recommendations and corresponding predictive outcomes (e.g., an initial asking price below the seller's profile to sell the exchange item within 6 hours, an initial asking price corresponding to the seller's profile to sell the exchange item within 11 hours, etc.). The server(s) 18 may further provide the predictive sales information to the seller's computing device.

The server(s) 18 perform the individual seller fraud detection functional block 724 to automate detection of a fraudulent seller and/or a fraudulent exchange item. This includes the seller verification and the exchange item verification as discussed in FIG. 4. The fraud detection further includes an automated process for resolving a potential fraud issue. For example, when a verification of seller falls between verified and not verified, the server(s) 18 evoke a process to render a definitive verification decision. As another example, when the verification of an exchange item falls between verified and not verified, the server(s) 18 evoke a process to render a definitive verification decision.

To extend the use of the marketplace to retailers or branded companies (i.e., the entity that initiates a gift card and ultimately accepts the gift card as payment), the server(s) 18 perform the retailer verification processing functional block 734 and the retailer sale processing functional block 736. The retailer verification processing functional block 734 includes one or more of setting up an account for a retailer to sell exchange items via the marketplace, verifying the retailer at least at the setup of the account and potentially for each transaction conducted via the marketplace, verifying the exchange items being offered for sale, and/or other verification mechanisms. As an example, a secure portal is established between the retailer seller and the marketplace server(s) 18 such that any communications via the secure portal is at least initially deemed a valid communication.

The retailer sale processing functional block 736 includes one or more of creating digital representations of the exchange items offered for sale, determining selling parameters and posting the digital representations and the parameters in the marketplace. The selling parameters include one or more of sales price, listing duration before changing price, restrictions, withdraw procedures, etc.

The server(s) 18 perform the buyer fraud detection functional block 740 to automate detection of a fraudulent buyer and/or fraudulent financial information used for purchasing. This includes the buyer verification and the purchase verification as discussed in FIG. 4. The fraud detection further includes an automated process for resolving a potential fraud issue. For example, when a verification of buyer falls between verified and not verified, the server(s) 18 evoke a process to render a definitive verification decision. As another example, when the verification of financial information falls between verified and not verified, the server(s) 18 evoke a process to render a definitive verification decision.

The server(s) 18 perform the payment processing functional block 748 to process payment through the user e-wallets of the seller and of the buyer. For instance, payment by the buyer is made from the buyer's e-wallet by debiting a credit card, a checking account, a savings account, a currency balance (e.g., money on account for purchases), and/or marketplace credit. Payment to the seller is made by crediting the seller's e-wallet with currency, marketplace credit, and/or some form of financial receipt. The mechanics of the payment process include the functionality described in FIG. 4.

The server(s) 18 perform the consumer profiles functional block 744 for a buyer. For the buyer, its consumer profile includes data regarding exchange item purchases of the buyer. The data includes one or more of the exchange items purchased, frequency of purchases, average purchase price, average value of purchased like exchange items (e.g., coffee shop gift cards), preferred discounts, etc. Note that this may be included in the buyer's e-wallet or maintained as a separate file.

The server(s) 18 perform the market customization functional block 746 to customize marketing of exchange items being offered for sale to particular buyers based on their buyer profiles. The market customization functional block 746 further includes determining a type and a quantity of exchange items a retailer should offer for sale and directing marketing efforts to a particular segment of buyers. In this manner, the system 10A efficiently and effectively couples exchange items for sale to buyers who typically buy such exchange items.

The server(s) 18 perform the individual sales processing function block 726, the bulk seller verification processing functional block 730, the bulk sale processing functional block 732, and the purchase processing functional block 742 as described with reference to one or more of FIGS. 1 and 4. The server(s) 18 also perform the displaying exchange items for sale functional block 728 to add/remove/edit an exchange item in the marketplace 700 as described with reference to one or more of FIGS. 1 and 4.

FIG. 6 is a schematic block diagram of another embodiment of an exchange item marketplace network that includes the network 24 of FIG. 1, an exchange item (EI) issuing server 920, and EI trusted module 922, a merchant server 924, the marketplace database 20 of FIG. 1, the marketplace server 18 and FIG. 1, an EI buyer computing device 926, and an initial owner computing device 928. The EI issuing server 920 may be implemented utilizing one or more of the brand server(s) 26 of FIG. 1, the processor server 28 of FIG. 1, and the distributor server 30 FIG. 1. The EI trusted module 922 may be implemented within one or more of the EI issuing server 920, the merchant server 924, and the marketplace server 18. The merchant server 924 may be implemented utilizing one or more of the retail server 34 of FIG. 1 and the point-of-sale equipment 32 of FIG. 1. The EI buyer computing device 926 may be implemented utilizing the buyer's computing device 16 of FIG. 4. The initial owner computing device 928 may be implemented utilizing the seller's computing device 12 of FIG. 4.

The marketplace database 20 includes a variety of databases, such as an agreement database 930, a user database 932, and an exchange item database 934. Each of the databases will be discussed in greater detail with reference to following figures. The marketplace server 18 includes a variety of processing capability, which may be implemented as a plurality of processing modules. In an embodiment, the marketplace server 18 includes a set of processing 936, a sale processing 938, a use processing 940, and a rule processing 942. Each of the processing modules will be discussed in greater detail with reference to following figures.

The EI buyer computing device 926 includes a digital wallet 944 and the initial owner computing device 928 includes another digital wallet 946. Each of the digital wallets 944-946 is utilized to store a variety of information associated with one or more exchange items, such as balance information, pricing information, history of sale, brand affiliation, rules, conditions, use options, owner information, and security information to ensure trust of the content of the digital wallet.

FIG. 7A is a schematic block diagram of another embodiment of an exchange item marketplace network that includes an EI distributor 800, the seller's computing device 12, the MP server(s) 18, the database 20, the buyer's computing device 16, and a retailer computing device 802. Alternatively, the MP server may include the database 20, where the virtual marketplace of exchange items 22 is stored as one or more transaction block chains of a secure custody protocol. The EI distributor 800 may be implemented utilizing one or more of the distributor servers 30 of FIG. 1, the brand server(s) 26 of FIG. 1, the MP server 18, and a merchant server (e.g., any entity acting on behalf of a brand in a distributor role). The retailer computing device 802 may be implemented utilizing one or more of the point-of-sale (POS) equipment 32 of FIG. 1, a merchant server, and the retail servers 34 of FIG. 1. The seller's computing device 12 includes the marketplace interface 142. The buyer's computing device 16 includes the marketplace interface 142 and the flash memory 92 of FIG. 2. The marketplace interface 142 includes the mobile app 198 of FIG. 4. The exchange item marketplace network functions to generate a transactions blockchain while facilitating a plurality of exchange item transactions. For example, a transactions blockchain is maintained for each exchange item. As another example, the transactions blockchain is maintained for a plurality of exchange items. As yet another example, a single transactions blockchain is maintained for all the exchange items for the entire virtual marketplace of exchange items 22. The transactions blockchain includes a block associated with each transaction of the plurality of exchange item transactions. Each block includes a header section and a transaction section. A structure of the transactions blockchain is discussed in greater detail with reference to FIGS. 7B-C.

In an example of operation of the generating of the transactions blockchain, the EI distributor 800 generates a block 0 of the transactions blockchain to establish exchange item (EI) information when determining to offer an exchange item for sale. The determining may be based on one or more of receiving a purchase request from the seller's computing device 12, receiving a bulk EI creation request, receiving the EI information from one or more of a branded company server and a processor service, and interpreting a schedule. For example, the EI distributor 800 determines to establish the EI information when receiving, via the processor service, EI information for a plurality of exchange items from the branded company server. As another example, the EI distributor 800 determines to establish the EI information when receiving, via a retail point-of-sale device, a purchase request for the EI from the seller's computing device 12.

Having determined to offer the EI for sale, the EI distributor 800 obtains the EI information. The obtaining includes receiving the EI information from the processor service and generating the EI information. The generating the EI information includes obtaining one or more of available balance, serial number, personal identification number (PIN), brand, EI type, expiration date, pricing approach, purchase restrictions, a hash of one or more of the elements of the EI information (e.g., a secure hash of the EI type using a private key of a private/public key pair of the brand server(s) 26), and the public key of the private/public key pair of the brand server(s) 26. Having obtained the EI information, the EI distributor 800 generates the block 0 to include the EI information.

The generating of the block 0 includes populating the block zero with a representation of the EI information and establishing trust for the block 0 utilizing a trust approach. The trust approach includes at least one of a digital signature approach utilizing a private key of a private/public key pair of the EI distributor 800 and encrypting the EI information utilizing the private key of the private/public key pair of the EI distributor 800 to produce the representation of the EI information. For example, the EI distributor 800 encrypts the EI information and the public key of the EI distributor 800 utilizing the private key of the EI distributor 800 to produce the transaction section of the block 0 when utilizing the encryption trust approach. As another example, the EI distributor 800 utilizes the private key of the EI distributor 800 to generate a digital signature over the EI information and the public key of the EI distributor 800 to produce the transaction section of the block 0.

When receiving the EI purchase request from the seller's computing device 12, the EI distributor 800 generates a block 1 of the EI transactions chain to indicate that the seller's computing device 12 is purchasing the EI from the EI distributor 800, where the block 1 is chained to the block 0 in accordance with a trusted chaining approach, and where the block 1 is generated utilizing the trust approach (e.g., as utilized when generating the block 0). The trusted chaining approach is discussed in greater detail with reference to FIG. 7C.

The generating of the block 1 includes generating seller to distributor payment information 1 (e.g., purchase price of this transaction, a timestamp of this transaction, purchaser identifier, and the transaction portion of the previous block), and establishing trust for the block 1 utilizing the trust approach. For example, the EI distributor 800 obtains a public key of a private/public key pair of the seller's computing device 12, encrypts the seller to distributor payment information 1 and the public key of the seller's computing device 12 utilizing the private key of the EI distributor 800 to produce the transaction portion of the block 1 when utilizing the encryption trust approach. As another example, the EI distributor 800 utilizes the private key of the EI distributor 800 to generate a digital signature over the seller to distributor payment information 1 and the public key of the seller's computing device 12 to produce the transaction section of the block 1.

Having generated the block 1 chained to the block 0, the EI distributor 800 issues secure EI information 804 to the seller's computing device 12. The issuing includes generating the secure EI information 804 to include the EI transactions chain (e.g., blocks 0-1) and sending the secure EI information 804 to the seller's computing device 12.

When determining to offer the EI for sale via the virtual marketplace of exchange items 22, the seller's computing device 12 issues secure EI information 806 to the MP servers 18, where the secure EI information 806 includes one or more of the secure EI information 804 and a request to sell the EI via the virtual marketplace of exchange items 22. Having received the secure EI information 806, MP servers 18 communicates pricing information 808 with the seller's computing device 12, where the pricing information 808 includes one or more of a desired price, a desired price range, a recommended price range, a recommended price, and a confirmed price.

Having communicated the confirmed price, the seller's computing device 12 and the MP servers 18 communicates secure sale information 810. For example, the MP servers 18 updates inventory information 809 (e.g., brand, balance, price, expiration date, volume, pricing rules by brand, etc.) to provide a representation of the EI for storage in the database 20 based on the transaction portion of the block 1, the MP servers 18 provides a public key of a private/public key pair of the MP servers 18 to the seller's computing device 12, and the seller's computing device 12 generates a block 2 of the EI transactions chain to indicate that the MP servers 18 is representing the EI for purchase by a buyer's computing device 16, where the block 2 is chained to the block 1 in accordance with the trusted chaining approach, and where the block 2 is generated utilizing the trust approach (e.g., as utilized when generating the block 1).

The generating of the block 2 includes generating a marketplace to seller representation and/or payment information 2 (e.g., desired price, a timestamp of this transaction, purchaser identifier, and the transaction portion of the previous block), and establishing trust for the block 2 utilizing the trust approach. For example, the seller's computing device 12 obtains the public key of a private/public key pair of the MP servers 18, encrypts the seller representation and/or payment information 2 and the public key of the MP servers 18 utilizing the private key of the seller's computing device 12 to produce the transaction section of the block 2 when utilizing the encryption trust approach. As another example, the seller's computing device 12 utilizes the private key of the seller's computer device 12 to generate a digital signature over the seller representation and/or payment information 2 and the public key of the MP servers 18 to produce the transaction portion of the block 2.

Having generated the block 2 chained to the block 1, the seller's computing device 12 issues the secure sale information 810 to the MP servers 18. The issuing includes generating the secure sale information 810 to include the EI transactions chain (e.g., blocks 0-2) and sending the secure sale information 810 to the MP servers 18.

When determining to purchase the EI for sale via the virtual marketplace of exchange items 22, the buyer's computing device 16 issues an EI purchase request 812 to the MP servers 18, where the EI purchase request 812 includes a request to purchase the EI (e.g., buyer's computing device 16 identifier, public key of a private/public key pair of the buyer's computing device 16, a purchase price, etc.). Having received the EI purchase request 812, the MP servers 18 communicate secure buyer wallet information 814 with the buyer's computing device 16. For example, the buyer's computing device 16 sends payment instructions to the MP servers 18 (e.g., purchase price, payment account information), the MP servers 18 generates a block 3 of the EI transactions chain to indicate that the buyer's computing device 16 is purchasing the EI for the purchase price amount, where the block 3 is chained to the block 2 in accordance with the trusted chaining approach, and where the block 3 is generated utilizing the trust approach (e.g., as utilized when generating the block 2).

The generating of the block 3 includes generating buyer to marketplace payment information 3 (e.g., a confirmed purchase price, payment instructions, a timestamp of this transaction, purchaser identifier, and the transaction portion of the previous block), and establishing trust for the block 3 utilizing the trust approach. For example, the MP servers 18 obtains the public key of the private/public key pair of the buyer's computing device 16, encrypts the buyer to marketplace payment information 3 and the public key of the buyer's computing device 16 utilizing the private key of the MP servers 18 to produce the transaction section of the block 3 when utilizing the encryption trust approach. As another example, the MP servers 18 utilizes the private key of the MP servers 18 to generate a digital signature over the buyer to marketplace payment information 3 and the public key of the buyer's computing device 16 to produce the transaction section of the block 3.

Having generated the block 3 chained to the block 2, the MP servers 18 issues secure buyer wallet information 814 to the buyers computing device 16. The issuing includes generating the secure buyer wallet information 814 to include the EI transactions chain (e.g., blocks 0-3) and sending the secure buyer wallet information 814 to buyer's computing device 16, where the mobile app 198 facilitates storage of the transactions chain as a secure EI record 822 in the flash memory 92.

When the buyer's computing device 16 determines to utilize the EI for payment of a transaction with the retailer computing device 802, the buyer's computing device 16 sends a transaction request 816 to the retailer computing device 802, where the transaction request 816 includes one or more of a retail transaction identifier of the transaction with the retailer computing device 802, and payment instructions that identifies the EI.

Having received the transaction request 816, the retailer computing device 802 and the buyer's computing device 16 communicate secure balance verification 818. The communicating of the secure balance verification information 818 includes the buyer's computing device 16 sending one or more of the secure EI record 822 (e.g., blocks 0-3) to the retailer computing device 802 and the public key of the private/public key pair of the MP servers 18.

Having received the secure EI record 822, the retailer computing device 802 verifies that a sufficient balance level is associated with the secure EI record 822 to facilitate completion of the transaction request 816. For example, the retailer computing device 802 decrypts the secure transaction section of the secure EI record 822 utilizing the public key of the MP servers 18 to reveal the balance level and a public key of the buyer's computing device 16 for verification with a public key received directly from the buyer's computing device 16. The retailer computing device 802 indicates favorable verification when the revealed balance level is sufficient and the received public key from the buyer's computing device 16 compares favorably (e.g., substantially the same) to the revealed public key from the secure EI record 822. As another example, the retailer computing device 802 verifies a signature over the secure transaction portion of the secure EI record 822 utilizing the public key of the MP servers 18 to verify the balance level and to verify the public key of the buyer's computing device 16. The retailer computing device 802 indicates favorable verification when the verified balance level is sufficient and the public key from the buyer's computing device 16 is verified from the secure EI record 822. As yet another verification example, the retail computing device 802 decrypts the hash of the one or more of the elements of the EI information using the private key of the EI distributor 800 (e.g., or a brand server(s) 26) and indicates favorable verification when the decrypted hash is substantially the same as a calculated hash over the one or more of the elements of the EI information. As such, the EI can be considered a legitimately issued EI from the brand server(s) 26 (e.g., from the brand owner).

When the verifications are favorable, the retailer computing device 802 and the buyer's computing device 16 communicate secure transaction completion 820. For example, the buyer's computing device 16 sends payment instructions to the retailer computing device 802 (e.g., purchase price, EI information), the buyer's computing device 16 generates a block 4 of the EI transactions chain to indicate that the buyer's computing device 16 is utilizing the EI for the purchase price amount, where the block 4 is chained to the block 3 in accordance with the trusted chaining approach, and where the block 4 is generated utilizing the trust approach (e.g., as utilized when generating the block 3).

The generating of the block 4 includes generating buyer to retailer payment information 4 (e.g., a confirmed purchase price, payment instructions utilizing the EI, a timestamp of this transaction, purchaser identifier, and the transaction portion of the previous block), and establishing trust for the block 4 utilizing the trust approach. For example, the buyer's computing device 16 obtains the public key of the private/public key pair of the retailer computing device 802, encrypts the buyer to retailer payment information 4 and the public key of the retailer computing device 802 utilizing the private key of the buyer's computing device 16 to produce the transaction section of the block 4 when utilizing the encryption trust approach. As another example, the buyer's computing device 16 utilizes the private key of the buyer's computing device 16 to generate a digital signature over the buyer to retailer payment information 4 and the public key of the retailer computing device 802 to produce the transaction section of the block 4.

Having generated the block 4 chained to the block 3, the buyer's computing device 16 issues the secure transaction completion 820 to the retailer computing device 802. The issuing includes generating the secure transaction completion 820 to include the EI transactions chain (e.g., blocks 0-4) and sending the secure transaction completion 820 to the retailer computing device 802, where the mobile app 198 may facilitate storage of an updated transactions chain as an updated secure EI record 822 in the flash memory 92. Alternatively, or in addition to, each of the seller's computing device 12, the MP servers 18, and the buyer's computing device 16 may validate information within the EI transactions chain by validating the chaining of each block to a next block utilizing the trusted chaining approach and may further validate information with the EI transactions chain by validating integrity of the transaction section of one or more of the blocks utilizing the trust approach (e.g., verifying a signature, decrypting an encrypted transaction to reveal a public key for verification).

In another example of operation of the generating of the transactions blockchain, at least one of the EI distributor 800, the seller's computing device 12, and the MP server(s) 18, authenticates value of an exchange item to produce an authenticated value of the exchange item. The exchange item includes one of a closed loop financial instrument and a digital good. The authenticating of the value includes a variety of authenticating approaches.

A first authenticating approach includes the seller's computing device 12 authenticating the value of the exchange item via a communication with a brand server (e.g., issue an authentication request, interpret a received verification response to identify an available balance of the exchange item associated with the brand server), generating a secure exchange item package, and securely passing, by the seller's computing device 12 to the marketplace servers 18, control over the secure exchange item package such that the marketplace server 18 obtains the control over the secure exchange item package. The securely passing includes updating a transaction section of the secure exchange item package by including a public key of a recipient device (e.g., the marketplace servers 18) of the secure exchange item package and signing the secure exchange item package by a transferring device (e.g., the seller's computing device 12) of the secure exchange item package. The secure exchange item package includes a header section and a transaction section. The secure exchange item package is discussed in greater detail with reference to FIG. 7C. A second authenticating approach includes the MP server(s) 18 authenticating the value of the exchange item via the communication with the brand server, generating the secure exchange item package, and obtaining control over the secure exchange item package as a result of being an originator of the secure exchange item package.

With the authenticated value of the exchange item produced, the marketplace servers 18 obtains control over the secure exchange item package, where the secure exchange item package includes identity of the exchange item, identity of an authenticated owner of the exchange item, identity of the marketplace server, and the authenticated value (e.g., face value of the exchange item or remaining balance of the exchange item) of the exchange item and where only a device possessing control over the secure exchange item package may modify the secure exchange item package.

As an example of the obtaining of the control, the marketplace servers 18 receives from the seller's computing device 12, a request to sell the exchange item (e.g., receives the secure EI information 806). In response to valid processing of the request to sell (e.g., communicating pricing information 808), the seller's computing device 12 securely passes, to the marketplace servers 18, control over the secure exchange item package (e.g., communicates secure sale information 810). Having obtained control, the marketplace servers 18 lists a representation of the exchange item for sale by storing associated inventory information 809 in the database 20 to update the virtual marketplace of exchange items 22.

With the exchange item represented within the virtual marketplace of exchange items 22, the marketplace server 18 receives, from the buyer's computing device 16, a request to purchase the exchange item (e.g., the EI purchase request 812). Having received the request to purchase the exchange item, the marketplace servers 18, in response to valid processing of the request to purchase the exchange item (e.g., exchanging secure buyer wallet information 814), securely passes to the buyer computing device 16, control over the secure exchange item package (e.g., via the secure buyer wallet information 814). Having received the secure buyer wallet information 814, the mobile app 198 stores the secure buyer wallet information 814 as the secure EI record 822 in the flash memory 92.

For use of the exchange item (e.g., as initiated with the transaction request 816), the buyer computing device 16 securely passes, to the retailer computing device 802 (e.g., the merchant server), control over the secure exchange item package. The use may further include the retailer computing device 802 into verifying that the balance of the exchange item is sufficient for a purchase transaction by communicating secure balance verification 818 with the buyer's computing device 16.

With control over the secure exchange item package, the merchant server (e.g., the retailer computing device 802) executes use of the exchange item by updating the value of the exchange item to produce an updated value of the exchange item. For example, the retailer computing device 802 subtracts an amount of the purchase transaction (e.g., for goods provided by a retailer to a user of the buyer's computing device 16) from the value of the exchange item to produce the updated value of the exchange item.

Having generated the updated value of the exchange item, the retailer computing device 802 generates an updated secure exchange item package, where the updated secure exchange item package includes identity of the exchange item, identity of the merchant server, identity of the buyer computing device, and the updated value of the exchange item. Having generated the updated secure exchange item package, the merchant server (e.g., the retailer computing device 802) securely passes control over the updated secure exchange item package to the buyer's computing device 16 (e.g., by communicating the secure transaction completion 820).

Alternatively, or in addition to, for a second use of the exchange item, the buyer's computing device 16 securely passes, to a second merchant server, control over the updated secure exchange item package. The second merchant server executes the second use of the exchange item by updating the updated value of the exchange item to produce a second updated value of the exchange item, generating a second updated secure exchange item package, where the second updated secure exchange item package includes identity of the exchange item, identity of the second merchant server, identity of the buyer's computing device 16, and the second updated value of the exchange item, and securely passes, to the buyer's computing device 16, control over the second updated secure exchange item package.

FIG. 7B is a schematic block diagram of a transactions blockchain where the transactions blockchain includes a plurality of blocks. The transactions blockchain represents an exchange item (EI) transaction chain when the plurality of blocks include exchange item transaction sections. Each block includes a header section and a transaction section. Each other portion links one block to other block in a sequential fashion. The linking is discussed in greater detail with reference to FIG. 7C. The transaction section includes EI transaction information associated with an EI transaction between two or more entities of an exchange item marketplace. For example, the block 0 includes valuable establishment 0 transaction information with regards to a genesis of a particular exchange item to be available to entities of the exchange item marketplace, the block 1 includes seller to distributor payment information 1 transaction information with regards to the seller's computing device 12 purchasing the EI from the EI distributor 800, the block 2 includes marketplace servers 18 to seller representation/payment information 2 transaction information with regards to the seller's computing device 12 offering the EI for sale utilizing the MP servers 18, the block 3 includes buyer to marketplace payment information 3 transaction information with regards to the buyer's computing device 16 purchasing the EI via the MP servers 18 from the seller's computing device 12, and the block 4 includes buyer to retailer payment information 4 transaction information with regards to the buyer's computing device 16 utilizing the EI to complete a desired purchase transaction with the retailer computing device 802.

FIG. 7C is another schematic block diagram of a transactions blockchain. The transactions blockchain includes a plurality of blocks, where each block includes a secure exchange item package. Each secure exchange item package includes a header section and a transaction section. The header section includes one or more of a nonce, a hash of a preceding block of the secure exchange item package, where the preceding block was under control of a preceding device in a chain of control of the secure exchange item package, and a hash of a current block (e.g., a current transaction section) of the secure exchange item package, where the current block is under control of a current device in the chain of control of the secure exchange item package. The transaction section includes one or more of a public key of the current device, a signature of the preceding device, payment information regarding a change of control from the preceding device to the current device, and exchange item information that includes at least some of the identity of the exchange item, a brand of the exchange item, time restrictions of the exchange item, a digital image of the exchange item, the authenticated value, and use restrictions of the exchange item.

FIG. 7C further includes user devices 2-3 (e.g., the seller's computing device 12, the MP servers 18, the buyer's computing device 16, the retailer computing device 802) to facilitate illustration of generation of the secure exchange item package. Each user device includes a hash function, a signature function, and storage for a public/private key pair generated by the user device.

An example of operation of the generating of the secure exchange item package, when the user device 2 has control of the secure exchange item package and is passing control of the secure exchange item package to the user device 3 (e.g., the user device 3 is transacting an exchange with the user device 2), the user device 2 obtains the user 3 public key from the user device 3, performs a hash function 2 over the user 3 public key and the transaction 2 to produce a hashing resultant (e.g., preceding transaction to user device 2) and performs a signature function 2 over the hashing resultant utilizing a user 2 private key to produce a user 2 signature. Having produced the user 2 signature, the user device 2 generates the transaction 3 to include the user 3 public key, the user 2 signature, user 3 payment to the user 2 information, and EI information 2-3. The user 3 payment to the user 2 information includes payment instructions from user 3 to user 2. The EI information 2-3 includes an updated balance of the exchange item (e.g., after the transaction between the user device 3 and the user device 2), a serial number of the exchange item, an expiration date of the exchange item, a type of the exchange item, a brand identifier, an image, a personal identification number, and utilization rules for the exchange item.

Having produced the transaction 3 section of the block 3 (e.g., a secure exchange item package 3), a processing module (e.g., of the user device 2, of the user device 3, of a transaction mining server, of the marketplace server 18) generates the header section by performing a hashing function over the transaction section 3 to produce a transaction 3 hash, performing the hashing function over the preceding secure exchange item package (e.g., block 2) to produce a block 2 hash. The performing of the hashing function may include generating a nonce such that when performing the hashing function to include the nonce of the header section, a desired characteristic of the resulting hash is achieved (e.g., a desired number of preceding zeros is produced in the resulting hash).

Having produced the secure exchange item package 3, the user device 2 sends the secure exchange item package 3 to the user device 3. Having received the secure exchange item package 3, the user device 3 validates the received secure exchange item package 3. The validating includes one or more of verifying the user 2 signature over the preceding transaction section (e.g., transaction 2) and the actual user 3 public key utilizing the user 2 public key (e.g., a re-created signature function result compares favorably to user 2 signature) and verifying that an extracted user 3 public key of the transaction 3 compares favorably to the user 3 public key held by the user device 3. The user device 3 considers the received secure exchange item package 3 validated when the verifications are favorable (e.g., the available balance of the exchange item is trusted).

FIG. 7D is a logic diagram of an embodiment of a method for generating a transactions blockchain. In particular, a method is presented for use in conjunction with one or more functions and features described in conjunction with FIGS. 1-6, 7A-C, and also FIG. 7D. The method includes step 830 where a processing module of a computing device of one or more computing devices of an exchange item marketplace network authenticates value of an exchange item to produce an authenticated value of the exchange item, where the exchange item includes one of a closed loop financial instrument and a digital good.

As an example of the authenticating the value of the exchange item, a seller device authenticates the value of the exchange item via a communication with a brand server, generates a secure exchange item package, and securely passes, to the marketplace server, control over the secure exchange item package such that the marketplace server obtains the control over the secure exchange item package. The securely passing includes updating a transaction section of the secure exchange item package by including a public key of a recipient device of the secure exchange item package and signing the secure exchange item package by a transferring device of the secure exchange item package. The secure exchange item package includes a header section and a transaction section. As another example of the authenticating the value of the exchange item, the marketplace server authenticates the value of the exchange item via a communication with the brand server, generates the secure exchange item package, and obtains control over the secure exchange item package as a result of being an originator of the secure exchange item package.

The method continues at step 832 where the marketplace server obtains control over the secure exchange item package, where the secure exchange item package includes identity of the exchange item, identity of an authenticated owner of the exchange item, identity of the marketplace server, and the authenticated value (e.g., face value of the exchange item and/or a remaining balance of the exchange item) of the exchange item and where only a device possessing control over the secure exchange item package may modify the secure exchange item package. As an example of the obtaining of the control, the marketplace server receives, from the seller device, a request to sell the exchange item and in response to valid processing of the request to sell, the seller device securely passes, to the marketplace server, control over the secure exchange item package.

The method continues at step 834 where the marketplace server receives, from a buyer device, a request to purchase the exchange item. In response to valid processing of the request to purchase the exchange item, the method continues at step 836 where the marketplace server securely passes, to the buyer device, control over the secure exchange item package. For use of the exchange item, the method continues at step 838 where the buyer device securely passes, to a merchant server, control over the secure exchange item package.

The method continues at step 840 where the margin server executes use of the exchange item by updating the value of the exchange item to produce an updated value of the exchange item (e.g., deducting a purchase price of a purchase transaction from the value of the exchange item to produce the updated value the exchange item). The method continues at step 842 where the merchant server generates an updated secure exchange item package, where the updated secure exchange item package includes identity of the exchange item, identity of the merchant server, identity of the buyer device, and the updated value of the exchange item. The method continues at step 844 where the merchant server securely passes, to the buyer device, control over the updated secure exchange item package.

Alternatively, or in addition to, for a second use of the exchange item, the buyer device securely passes, to a second merchant server, control over the updated secure exchange item package. The second merchant server executes the second use of the exchange item by updating the updated value of the exchange item to produce a second updated value of the exchange item, generates a second updated secure exchange item package, where the second updated secure exchange item package includes identity of the exchange item, identity of the second merchant server, identity of the buyer device, and the second updated value of the exchange item, and securely passing, to the buyer device, control over the second updated secure exchange item package.

The method described above in conjunction with one or more of the processing module, the seller device, the marketplace server, the buyer device, the merchant server, the second merchant server, can alternatively be performed by other modules of the exchange item marketplace network or by other devices. In addition, at least one memory section (e.g., a non-transitory computer readable storage medium, a computer readable memory) that stores operational instructions can, when executed by one or more processing modules of one or more computing devices of the exchange item marketplace network, cause the one or more computing devices to perform any or all of the method steps described above.

FIG. 7E is a logic diagram of another embodiment of a method for generating a transactions blockchain. In particular, a method is presented for use in conjunction with one or more functions and features described in conjunction with FIGS. 1-6, 7A-D, and also FIG. 7E. The method includes step 850 where a processing module of a computing device (e.g., of an exchange item origination entity) of one or more computing devices of an exchange item marketplace network generates an origination block of an EI transaction chain, where the EI origination entity signs a transaction portion of the origination block, and where the transaction portion indicates EI information of an associated EI. For example, the origination entity generates value establishment information in accordance with a trust approach (e.g., self-signing over the value establishment information to produce the transaction portion, signing the value establishment information, that includes a public key of a private/public key pair of the EI origination entity, utilizing the private key to produce the transaction portion).

When receiving an EI purchase request from a seller computing device, the method continues at step 852 where a processing module of an EI distribution entity generates a first block of the EI transactions chain, where the EI distribution entity signs the transaction portion of the first block, where the transaction portion indicates that the seller computing device is purchasing the EI from the distribution entity, and where the first block is chained to the origination block in accordance with a chained security approach (e.g., hash of transaction portion, hash of a previous block). The EI distribution entity may be implemented utilizing the EI origination entity. For example, the EI distribution entity signs the transaction portion utilizing a private key of a private/public key pair of the seller computing device to produce the transaction portion of the first block.

When transacting a representation of the EI with a marketplace server, the method continues at step 854 where the seller computing device generates a second block of the EI transactions chain, where the seller computing device signs a transaction portion of the second block, where the transaction portion indicates that the MP server is representing the EI for the seller computing device, and where the second block is chained to the first block in accordance with the chained security approach. For example, the MP server receives secured EI information from the seller computing device (e.g., an offer for sale), provides pricing information to the seller computing device, receives a confirmed price from the seller computing device, issues secure sale information to the seller computing device, and updates inventory information within a virtual exchange item marketplace, where the secure sale information includes the second block of the EI transactions chain and a public key of the MP server.

When receiving a purchase request for the EI from a buyer computing device, the method continues at step 856 where the MP server generates a third block of the EI transactions chain, where the MP server signs a transaction portion of the third block, where the transaction portion indicates that the buyer computing device is purchasing the EI from the seller computing device via the marketplace, and where the third block is chained to the second block in accordance with the chained security approach. For example, the buyer computing device issues an EI purchase request to the MP server based on received inventory information from the MP server, the MP server generates secure buyer wallet information, the buyer computing device stores a security EI record, where the secure buyer wallet information includes the third block of the EI transactions chain and the secure EI record includes the EI transactions chain. For instance, the MP server signs a public key of the buyer computing device and the transaction portion utilizing a private key of a private/public key pair of the MP server to produce the transaction portion of the third block.

When utilizing the EI for payment in a purchasing transaction with a retailer computing device, the method continues at step 858 where the buyer computing device generates a fourth block of the EI transactions chain, where the buyer computing device signs a transaction portion of the fourth block, where the transaction portion indicates that the buyer computing device is utilizing the EI for payment in the purchasing transaction, and where the fourth block is chained to the third block in accordance with the chained security approach. For example, the buyer computing device issues a transaction request to the retailer computing device, the retailer computing device exchanges secure balance information with the buyer computing device (e.g., verifies the trust of the EI transactions chain, where the EI transactions chain indicates an available balance of the EI verifying that an available balance is sufficient), the retailer computing device issues secure transaction completion information to the buyer computing device, where the secure transaction completion information includes the fourth block of the EI transactions chain. The buyer computing device signs the public key of the retailer computing device and the transaction portion to produce a transaction portion of the fourth block. Alternatively, or in addition to, each entity of the plurality of transactions may verify the EI transactions chain by verifying a stored public key matches to recovered public keys when validating signatures over associated blocks.

The method described above in conjunction with the exchange item origination entity, the seller computing device, the buyer computing device, and the retailer computing device can alternatively be performed by other modules of the exchange item marketplace network or by other devices. In addition, at least one memory section (e.g., a non-transitory computer readable storage medium, a computer readable memory) that stores operational instructions can, when executed by one or more processing modules of one or more computing devices of the exchange item marketplace network, cause the one or more computing devices to perform any or all of the method steps described above.

FIG. 8A is a logic diagram of an embodiment of a method for utilizing an exchange item in an exchange item marketplace network. The method includes step 860 where a processing module (e.g., of a brand server, of a marketplace server) creates one or more exchange items to be offered for sale through the exchange item marketplace network. The method continues at step 862 where an initial owner acquires at least one of the EIs. The method continues at step 864 where a processing module of the exchange item marketplace network establishes initial conditions. Conditions includes types of conditions and values for the types of conditions. For example, a weather condition is associated with a value of a current temperature. As another example, a sports team score is associated with a particular game outcome. Other examples of condition types include stock prices, world events, purchase history of users associated with the exchange item marketplace, pricing history associated with exchange items, a physical location, a customer name, a merchant name, a brand-name, a date, a time, etc.

The establishing of the conditions includes utilizing the predetermination, interpreting the lookup, interpreting a query response, receiving the conditions, identifying the conditions based on or more of identification of the initial owner, identification of the brand of the EI, an EI type indicator, and EI serial number, and an EI utilization rule, etc. For example, the marketplace server performs a lookup based on a serial number of the exchange item to establish the initial conditions.

The method continues at step 866 where the processing module determines whether the EI has been used (e.g., redeemed, utilized for making a purchase, bartered, etc.). The determining includes interpreting a status associated with the EI of an exchange item database, interpreting a received a use message, receiving purchase transaction information, etc. the method branches to step 874 when the processing module determines that the EI has not been used. The method continues to step 868 when the processing module determines that the EI has been used.

When the EI has been used, the method continues at step 868 where the processing module processes the EI use. The processing includes one or more of facilitating completion of a purchase transaction, facilitating payment distribution, and updating the exchange item database to indicate the use. The method continues at step 870 where the processing module determines whether the EI is exhausted (e.g., no value left). The determining includes comparing a balance value associated with the EI to a minimum threshold level (e.g., zero dollars). For example, the processing module indicates that the EI has been exhausted when the balance value is zero. The method looks back to step 866 when the EI is not exhausted. The method continues to step 872 when the EI is exhausted where the EI is retired. Alternatively, and in accordance with a rule associated with exchange item, the processing module maintains the zero balance exchange item without retiring the exchange item (e.g., to keep open an opportunity to refresh the exchange item). The retiring includes the processing module updating the exchange item database to indicate that the EI has been exhausted and retired from use.

When the EI has not been utilized, the method continues at step 874 with a processing module determines whether the EI is to be offered for sale. The determining includes receiving a request to offer the EI for sale, interpreting a rule with regards to sale, interpreting a status associated with the EI, and receiving a purchase request for the EI. The method branches to step 878 when the EI is not to be offered for sale. The method continues to step 876 when the EI is to be offered for sale where the processing module posts the EI in the marketplace. For example, the processing module updates the exchange item database to indicate that the EI is for sale.

The method continues at step 878 where the processing module determines whether the EI has been sold. The determining includes one or more of receiving purchase transaction information, interpreting a request for purchase of the EI, and interpreting a status associated with the EI in the exchange item database. The method branches to step 882 when the EI has not been sold. The method continues to step 880 when the EI has been sold where the processing module processes the sale and updates information. For example, the processing module updates the exchange item database to indicate that the EI has been sold, the purchase amount, and identification of the (new) owner.

The method continues at step 882 where the processing module updates the conditions. For example, the processing module obtains updated date and time information, sports scores, stock market information, world events information, and weather information. With the conditions updated, utilization and sale of other exchange items may be affected as different use rules associated with the different exchange items may unable shifts in parameters associated with exchange items. For example, an additional discount for a particular branded exchange item may be enabled when a temperature value of a temperature condition is less than a low threshold value. As another example, a balance of another exchange item may be increased by 10% for a two-hour time frame when a local baseball team wins a game and the exchange item is associated with a brand of the local baseball team. Having updated the conditions, the method loops back to step 866

FIG. 8B is a logic diagram of an embodiment of a method for utilizing rules in an exchange item (EI) marketplace network. A rule is associated with utilization of an exchange item. The rule may be imposed by one or more of an issuing brand, a merchant, an alternative brand, and by a marketplace server of the exchange item marketplace. A rule specifies allowable values or ranges of values of parameters associated with an exchange item is a function of one or more conditions and of one or more use options. Rules be imposed independently (e.g., alone without any interaction with other rules), in series (e.g., first rule invoked followed by a second rule invoked), in parallel (e.g., operating two or more rules together, and may interact where a first rule status may be utilized by a second rule), or in a nested fashion (e.g., where a rule is triggered when a value associated with a preceding rule compares favorably to a trigger threshold level). Each EI rule is associated with a rule lifecycle, which includes creation of the EI rule, and may include invoking of the EI rule and updating of the EI rule and/or of an associated EI of the EI rule (e.g., updating a marketplace server database).

A method associated with the creation of the EI rule includes step 890 where a processing module (e.g., by a brand server, by a marketplace server) determines whether an exchange item (EI) rule has been invoked. The determining may be based on one or more of interpreting values of conditions in accordance with the EI rule, receiving a message indicating that the rule has been invoked, and detecting an activity associated with the invoking of the rule. The method branches to steps 892 and 894 when the EI rule has been invoked. The method branches to step 902 when the EI rule has not been invoked where the processing module determines whether the EI rule has changed. The determining may be based on one or more of interpreting a change flag, receiving a change message, observing activity associated with a change of the rule, and comparing a previous EI rule to the EI rule. The method continues to step 904 when the EI rule has not been changed where the processing module determines whether the EI rule has expired (e.g., detecting that an active timeframe associated with the EI rule has elapsed). The method loops back to step 890 when the EI rule has not expired.

When the EI rule has been invoked, the method continues at step 892 where the processing module notifies a current owner of the invoked EI rule (e.g., issuing a message to a brand server that established (i.e., owner) the rule) and the method continues at step 894 where the processing module updates the EI based on the invoked EI rule. The updating includes modifying a record of the EI in the marketplace server database immediately or upon receiving a permissions grant from the owner, modifying the record of the EI in the marketplace server database.

The method continues at step 896 where the processing module determines whether the EI rule has been revoked. The determining may be based on one or more of interpreting updated conditions associated with the EI rule and indicating that the EI rule has been revoked and receiving a message indicating that the EI rule has been revoked (e.g., from a brand server). The method loops back to step 890 when the EI rule has not been revoked. The method continues to steps 898 and 900 when the EI rule has been revoked. The method continues at step 898 where the processing module notifies the current owner of the revoked EI rule (e.g., issuing an EI revoked message) and updates the associated EI based on the revoked EI rule (e.g., updates the marketplace server database).

A method associated with the invoking of the EI rule includes step 906 where the processing module tracks conditions for exchange items of a rule set. For example, the processing module receives conditions data associated with a plurality of conditions types and maps the conditions data a plurality of exchange items associated with rules that rely on the conditions to activate a course of action. The method continues at step 908 where the processing module, per exchange item, determines when a condition conforms to a rule to invoke the rule. For example, the processing module indicates to invoke the rule when a condition of the rule meets a threshold level.

A method associated with the updating of the EI rule includes step 910 where the marketplace server takes control of the exchange item. The taking of control includes invoking a rule that includes granting updating authority for the marketplace server. With the authority to update the exchange item in the marketplace server database, the marketplace server may modify a rule, add a rule, delete a rule, add conditions associated with a rule, delete conditions associated with a rule, and modify conditions associated with a rule.

The method continues at step 912 where the marketplace server updates the exchange item. For example, the marketplace server recovers a portion (e.g., a single transaction blockchain including a ledger of all exchange items) of the marketplace server database and modifies the recovered portion (e.g., modifies the blockchain) to produce an updated portion of the marketplace server database. The method continues at step 914 where the marketplace server signs the updated exchange item. For example, the marketplace server utilizes a private key of a public/private key pair of the marketplace server to electronically sign the updated exchange item to produce a signature of the marketplace server. The method continues at step 916 where the marketplace server returns control of the signed updated exchange item. For example, the marketplace server stores the signed updated exchange item into the marketplace or database and pushes the signed updated exchange item to one or more entities of the exchange item marketplace network. For instance, the marketplace server sends the signed updated exchange item to a computing device associated with purchase of the exchange item. As another instance, the marketplace server sends the signed updated exchange item to a brand server associated with the exchange item. Such a signed updated exchange item is illustrated where exchange item serial number 5, that is associated with owner AA, includes conditions e3, f6, p5 that is associated with the exchange item 5, and that now follows a rule set 4.

FIG. 8D is a schematic block diagram of another embodiment of an exchange item marketplace network that includes the initial owner computing device 928 of FIG. 6, the EI issuing server 920 of FIG. 6, the EI trusted module 922 of FIG. 6, the marketplace server 18 of FIG. 6, and the marketplace database 20 of FIG. 6. Entities of the exchange item marketplace network may be operably coupled through the network 24 of FIG. 6 or may be directly connected to each other. The exchange item marketplace functions to establish agreements and set up exchange items. Such agreements include terms for one or more of creation of exchange items (EI), creation of EI rules for the exchange items, identification of condition types and condition values to be utilized in conjunction with the EI rules, and facilitating payment for sale and/or utilization of an exchange item. The agreements may involve two or more parties, such as a brand, a merchant, and an alternative brand. For example, an agreement between a brand and a merchant associated with the brand indicates a discount range associated with a particular exchange item. As another example, an agreement between a brand and the alternative brand indicates which products may be purchased using an exchange item not associated with the product. Agreement information includes one or more agreement points of each agreement (e.g., value, discount, balance, permissions, etc.).

In an example of operation of the establishing of the agreements and setting up of the exchange items, the setup (i.e., or set up) processing 936 of the marketplace server 18 establishes the agreement database 930. The establishing includes receiving agreement information and updating the agreement database 930 within the marketplace database 20. For example, the marketplace server 18 issues a query to one or more of the EI issuing server 920, another issuing server, a merchant server, another merchant server; and receives a query response. As another example, the marketplace server 18 receives an unsolicited message including the agreement information. Having received the agreement information, the marketplace server updates the agreement database 930. The agreement database 930 correlates issuer information, merchant information, and agreement information. For example, the agreement database 930 associates issuer A_1 with a merchant A_1_n as bound by an agreement aa (e.g., including one or more agreement points).

Having established the agreements, the marketplace server 18 facilitates setting up of the exchange items to include establishment of exchange item (EI) rules. An initiating entity establishes a first rule for a new exchange item. The initiating entity includes at least one of the EI issuing server 920 and the set of processing hundred and 36 of the marketplace server 18. The first rule is associated with establishment of a security approach to ensure that and subsequent rules associated with the EI can be trusted by all marketplace participants as time proceeds. For example, the EI issuing server 920 establishes trust information 954 to include a first contract block of a contract blockchain, where private/public key pairs are utilized to ensure trust as previously discussed with reference to FIGS. 7A-E. The first contract block establishes the EI issuing server 920 as the owner (e.g., a root of the contract blockchain).

The initiating entity further establishes the new exchange item. For example, the EI issuing server 920 establishes EI information 950 (e.g., value, type, issuance date, expiration date, use parameters, etc.). The initiating entity further establishes content of the first rule, and further content of other rules as an EI rule set 952. For example, the EI issuing server 920 utilizes a 4^(th) set of EI rules and an EI of serial number 5 for issuer B_K (e.g., identity of the EI issuing server 920) to include EI 05 info. The EI 005 is “for sale” and is bound by a fourth set of EI rules which are associated with conditions e3, f6, p5 in accordance with use options of the issuer B_K. Having obtained the EI information 950 and the EI rule set 952, the set up processing 936 verifies the received EI information and set by exchanging set up verification 956 with the EI trusted module 922. For example, the EI trusted module 922 verifies the contract blockchain and sends an indication of a status of the verification to the marketplace server 18.

When the EI information 950 in the EI rule set 952 have been verified, set of processing 936 updates the exchange item database 934 of the marketplace database 20 with the EI information 950 in the EI rule set 952. For instance, the setup processing 936 establishes the role of the exchange item database 934 associated with the EI serial number 005. The set of processing 936 may further update the user database 932 to include a list of known users of the marketplace, a history of EI buying, selling, and using. For example, the set of processing 936 updates the user database 932 when the initial owner computing device 928 (e.g., owner AA) purchases the new EI by exchanging set up information 958 with the marketplace server 18. The initial owner computing device 928 updates a digital wallet 946 of the initial owner computing device 928 with an owner table. The owner table includes one or more of a list of EI serial numbers, and for each EI, an identifier of an issuer, associated EI information, use options, EI rules associated with the EI, and conditions associated with the EI. Alternatively, or in addition to, the marketplace server maintains a copy of the owner table in the marketplace database 20.

FIG. 8E is a schematic block diagram of another embodiment of an exchange item marketplace network that includes the initial owner computing device 928 of FIG. 6, the EI buyer computing device 926 of FIG. 6, the EI trusted module 922 of FIG. 6, the marketplace server 18 of FIG. 6, and the marketplace database 20 of FIG. 6. The exchange item marketplace functions to process a sale of an exchange item (EI) from the initial owner computing device 928 to the EI buyer computing device 926.

In an example of operation of the processing of the sale of the EI serial number 005 by the initial owner computing device 928 (e.g., owner AA) the EI buyer computing device 926 (e.g., owner DZ), the sale processing 938 of the marketplace server 18 exchanges sale information 966 with the initial owner computing device 928, where the sale information 966 includes one or more of the EI serial number 005, a sale price, use options, a commission amount (e.g., to the marketplace), and credit information (e.g., a 05 credit of generic value usable in the marketplace to purchase another EI or to be converted into another form of payment). The initial owner computing device 928 updates the digital wallet 946 to indicate that the EI serial number 005 has been sold and that the 05 credit is available.

The sale processing 938 further exchanges sale verification 968 with the EI trusted module 922. For example, the EI trusted module 922 verifies the contract blockchain and a transaction blockchain associated with the EI to ensure that the sale is within sale allowance parameters associated with the EI as imposed by one or more of an agreement, and EI rule, conditions, and use options. When verified, the EI trusted module 922 issues the sale verification 968 to the sale processing 938 indicating that the sale is verified.

The sale processing 938 further exchanges purchase information 970 with the EI buyer computing device 926, such that the EI buyer computing device 926 updates the digital wallet 944 indicating that owner DZ has the EI serial number 005. Having processed the sale of the EI 005, the sale processing 938 updates the marketplace database 20 indicating that the EI serial 005 is now associated with owner DZ and is not currently for sale.

FIG. 8F is a schematic block diagram of another embodiment of an exchange item marketplace network that includes the EI buyer computing device 926 of FIG. 6, the EI trusted module 922 of FIG. 6, the merchant server 924 FIG. 6, the marketplace server 18 of FIG. 6, and the marketplace database 20 of FIG. 6. The exchange item marketplace functions to process use of an exchange item (EI) by the EI buyer computing device 926 with the merchant server 924.

In an example of operation of the use of the EI, the EI buyer computing device 926 obtains EI info from the digital wallet 944 to issue buyer use information 976 to the marketplace server 18 when desiring to utilize the exchange item (e.g., EI serial number 005) with a merchant associated with the merchant server 924 for purchase of goods and/or services. When receiving the buyer use information 976, the use processing 940 of the marketplace server 18 verifies the use by exchanging use verification 978 with the EI trusted module 922. The use verification 978 includes one or more of the buyer use information 976 and an associated row of the exchange item database 934 associated with the exchange item (e.g., the row associated with the exchange item serial number 005). For example, the EI trusted module 922 verifies that the use of the EI compares favorably with the associated rules, conditions, and use options.

When receiving favorable use verification 978, the use processing 940 exchanges merchant use information 980 with the merchant server 924 to complete the use of exchange item. Alternatively, the marketplace server 18 receives the merchant use information 980 from the merchant server 924 via the EI buyer computing device 926 as part of the buyer use information 976 (e.g., a secure blockchain element is generated by the merchant server 924 and communicated directly to the EI buyer computing device 926).

The merchant use information 980 includes one or more of the buyer use information 976, the use verification 978, and any additional information to complete the use of the EI. Upon completion of the use of the EI, the use processing 940 updates the exchange item database 934 indicating that the EI has been utilized (e.g., indicating an amount of an outstanding balance utilized and a remaining available balance etc.). Alternatively, or in addition to, the use processing 940 performs a merchant verification process in accordance with a rule associated with the exchange item. For example, the use processing 940 extracts security information from the merchant use information 980, exchanges use information 978 with the EI trusted module 922, and interprets a use verification 978 response from the EI trusted module 922 to determine whether the merchant server 924 is verified (e.g., non-fraudulent). The EI trusted module 922 may verify the merchant server 924 by a variety of approaches including accessing a database of fraudulent merchants, invoking a rule of an associated exchange item to test a plurality of parameters associated with the merchant use information 980, and requesting that the merchant server 924 electronically sign a message to verify that the merchant server 924 holds a correct private key associated with a previously verified merchant server 924.

FIG. 8G is a schematic block diagram of another embodiment of an exchange item marketplace network that includes the EI buyer computing device 926 of FIG. 6, the EI issuing server 920, the EI trusted module 922 of FIG. 6, the marketplace server 18 of FIG. 6, and the marketplace database 20 of FIG. 6. The exchange item marketplace functions to process rules associated with an exchange item (EI).

In an example of operation of the processing of the rules, the rule processing 942 of the marketplace server 18 records conditions for a plurality exchange items. A condition of the conditions for the plurality of exchange items further includes one of a range of time, a range of dates, a geographic location, a building address, a list of items, a user tendency profile, and a user loyalty profile. For example, the marketplace server 18 obtains the condition from a corresponding condition source.

For an exchange item of the plurality of exchange items, where the exchange item has a quantifiable value (e.g., valid tender, offered something formally in writing, offered a sum for a settlement, same as money, offer made to settle something), a serial number, and a current owner, the rule processing 942 determines whether a corresponding condition of the exchange item is compliant with one or more rules of an applicable set of rules (e.g., a contract regarding the exchange item from the issuer, where a set of rules is utilized for each EI, or for a group of EIs, for each owner, by brand, by retailer, etc.). The determining includes utilizing a sliding scale of compliance (e.g., conditional chaining) based on one or more of a user profile, exchange item information, an exchange item issuer, limited exchange item use, and timing of use. For example, the rule processing 942 obtains information with regards to conditions and EI rules from the exchange item database 934 and interprets conditions data in accordance with the EI rules to determine the compliance. For example, the rule processing 942 indicates that a weather rule is compliant when a temperature condition indicates a temperature value that is greater than a temperature threshold value associated with the weather rule.

The rule processing 942 may verify the compliance with the EI rule by obtaining issuer rule information 986 from the EI issuing server 920 associated with the EI and by further verifying compliance by exchanging rule verification 990 with the EI trusted module 922. The verifying of compliance further includes verifying a security scheme (e.g., contract blockchain or the EI rules) and by checking that the EI rule compares favorably to the issuer rule information 986 from the EI issuing server 920.

The rule processing 942 may update the applicable set of rules based on one or more of a rule changing, a rule expiring, and a new rule being added to the set. For example, the rule processing 942 updates the exchange item database 934 and sends owner rule info 988 to the EI buyer computing device 926 to indicate an EI rule change associated with a particular EI when current conditions and a previous rule indicate changing the rule when the conditions are compliant.

The rule processing 942 may further determine a specific use as the one or more rules of the applicable rule set (e.g., for a specific product, a specific store, etc.). For example, the rule processing 942 identifies raising a discount level for the exchange item in accordance with the EI rule as the specific use in accordance with the EI rule and favorable conditions to alter the discount level. Alternatively, or in addition to, the rule processing 942 determines a specific time frame as the one or more rules of the applicable rule set (e.g., for a set period of time, a day, etc.). For example, the rule processing 942 identifies a two-hour time window for the raised discount level for the exchange item in accordance with the one or more rules.

When the corresponding condition of the exchange item is compliant with the one or more rules, the rule processing 942 establishes a secure communication with a computing device affiliated with a current owner (e.g., of the exchange item and/or of the contract blockchain) to take control of the exchange item (e.g., to update an exchange item record of the exchange item). Having control includes holding a private key associated with modifying a blockchain associated with the exchange item. For example, the rule processing 942 exchanges a secure owner rule information 988 with the EI buyer computing device 926 associated with an exchange item serial number 005, where the rule processing 942, in accordance with a security rule, is allowed to modify the contract blockchain with regards to the EI rules.

While having control over the exchange item, the rule processing 942 securely modifies the quantifiable value of the exchange item based on the one or more rules to produce a modified exchange item. For example, the rule processing 942 adds another contract block to the contract blockchain, where the additional contract block includes a modified exchange item as modified exchange item info serial number 005. The modifying of the quantifiable value includes increasing the quantifiable value for the specific use when the specific use is utilized as the one or more rules of the applicable rule set and securely modifying the quantifiable value of the exchange item in accordance with the blockchain protocol.

Having modified the quantifiable value of the modified exchange item, the rule processing 942 sends a notification message (e.g., owner rule information 988) to the computing device (e.g., the EI buyer computing device 926) regarding the increased quantifiable value and the specific use. Having received the notification message, the EI buyer computing device 926 stores the (modified) exchange item in accordance with the blockchain protocol (e.g., stores the contract blockchain including the new contract block in the digital wallet 944).

The modifying of the quantifiable value may further include increasing the quantifiable value for use during the specific time frame when the specific time frame is utilized as the one or more rules of the applicable rule set (e.g., an increase discount level for the next two hours). Having modified the quantifiable value, the rule processing 942 sends another notification message to the computing device regarding the increased quantifiable value and the specific time frame.

While having control over the exchange item, the rule processing 942 further prevents the computing device or another computing device from accessing the exchange item. For example, the rule processing 942 issues owner rule information 988 to the EI buyer computing device 926 indicating that the exchange item is not to be utilized while being modified. Alternatively, or in addition to, the rule processing 942 updates the exchange item database 934 indicating that the exchange item is not to be accessed while being modified. When completing the modification, the rule processing 942 releases, via the secure communication, control of the modified exchange item to the computing device affiliated with the current owner. For example, the rule processing 942 issues yet another owner rule information 988 to the EI buyer computing device 926 indicating that the exchange item has been updated and released.

With the exchange item updated, and when the specific time frame expires (e.g., when utilized) and the modified exchange item is unused (e.g., the EI buyer computing device 926 has not used the modified exchange item at all), the rule processing 942 facilitates reverting of the exchange item. The reverting of the exchange item includes one or more of establishing another secure communication with the computing device affiliated with exchange item to take control of the modified exchange item and while having control over the modified exchange item, decreasing the increased quantifiable value to the quantifiable value to produce a reverted exchange item, preventing the computing device or another computing device from accessing the exchange item, releasing, via the other secure communication, control of the reverted exchange item to the computing device affiliated with the current owner, and sending another notification message to the computing device regarding the reverted exchange item.

Alternatively, when the specific time frame expires, and the modified exchange item was used but did not exhaust the quantifiable value, the rule processing 942 facilitates producing a further modified EI. The facilitating to produce the further modified EI includes one or more of identifying another rule of the applicable set of rules to further modify the modified exchange item, establishing another secure communication with the computing device affiliated to take control of the modified exchange item, and while having control over the modified exchange item, the rule processing 942 increases a remaining quantifiable value to produce a further modified exchange item, prevents the computing device or another computing device from accessing to the modified exchange item, releases, via the other secure communication, control of the further modified exchange item to the computing device affiliated with the current owner, and sends another notification message to the computing device regarding the further modified exchange item.

With the modified exchange item, the EI buyer computing device 926 may utilize the modified exchange item in conjunction with a purchase transaction from a merchant. For example, the EI buyer computing device 926 sends a use request to another server (e.g., a merchant server) regarding the modified exchange item (e.g., to utilize the modified EI for the purchase transaction). Having received the use request, the other server sends a use notification to the marketplace server 18. Having received the use notification, the rule processing 942 of the market place over 18 establishes a second secure communication with the computing device affiliated with the current owner to take control of the modified exchange item (e.g., exchanges owner rule information 988 with the EI buyer computing device 926).

While having control over the exchange item, the marketplace server 18 securely adjusts the quantifiable value of the exchange item based on the use notification to produce an adjusted exchange item (e.g., decrements a remaining balance by an amount of the purchase transaction and updates one or more of a transaction blockchain and the contract blockchain) and prevents the computing device, the other server, or other computing devices from accessing the exchange item. Once modified, the marketplace server 18 releases, via the second secure communication, control of the adjusted exchange item to the computing device affiliated with the current owner.

FIG. 8H is a diagram of an exchange item (EI) database 934 that includes a variety of fields. The variety of fields includes an EI serial number, and issuer, and owner, EI information, conditions, EI rules, offer for sale, use options, blockchain control, and blockchain location when a blockchain approach is utilized as a security mechanism for entities trading in the EI to verify attributes associated with the EI. For example, a transaction blockchain is associated with transactions from birth of the EI to complete utilization/retirement of the EI and a contract blockchain associated with EI rule changes as time progresses. A structure of the transaction blockchain and the contract blockchain is discussed in greater detail with reference to FIG. 8J.

To ensure favorable security, a controlling entity desiring to modify the blockchain must be associated with control of the blockchain as indicated by the blockchain control field of the exchange item database 934. The controlling entity may change from one entity to another during the EI lifecycle and may further be constrained as indicated by the EI rules. For example, a particular blockchain may be controlled by the EI issuer in the beginning and later controlled by the marketplace server in accordance with the EI rules established by the EI issuer. As another example, the blockchain may be controlled by the merchant server to update rules and conditions to support a particular promotion as allowed by the original and current EI rules.

A most recent revision of a particular blockchain may be temporarily stored in one or more entities of the exchange item marketplace as indicated by the blockchain location field. As such, the controlling entity may utilize the exchange item database 934 to identify the entity where the blockchain is temporarily stored to gain access to the blockchain for modification in accordance with the rules and conditions.

FIG. 8J is another schematic block diagram of a transactions blockchain that includes a series of transaction blocks. Each transaction block includes a security bridge from a last block to this block (e.g., hash over previous block and a previous nonce, and a hash over a current block and a current nonce), transaction information, a signature by a current seller over the transaction info, and a contract blockchain. The transaction information includes a next purchaser public key (e.g., a public key of a public/private key pair of the next purchaser associated with a next transaction), payment information, and EI information. The payment information includes payment information (e.g., payment amount, payment source, etc.) from the next purchaser to the current seller associated with the current block. The signature is created by the current seller signing the transaction information utilizing the private key of a public/private key pair of the current seller.

The contract blockchain includes one or more contract blocks representing changes to rules and/or conditions of the EI of the EI information. For example, the contract blockchain includes a complete contract blockchain for substantially all of the rules and/or conditions changes. As another example, the contract blockchain includes at least one contract block associated with the transaction block. Alternatively, or in addition to, the contract blockchain is maintained separately and is not included within the transaction block. Further alternatively, a single combined transaction and contract blockchain is maintained as one entity.

Each contract block includes a security bridge from a last block to this block, a contract package (from a last contract block to this contract block), and a signature by a current rules owner over the contract package. Each contract package includes at least one next owner public key (e.g., associated with an exchange item marketplace entity expected to be a next owner of the contract blockchain), and contract information. The contract information includes one or more of EI rules, conditions, use options, EI information, agreements, merchant identifiers, issuer identifier, EI serial number, owner identifier, an offer for sale indicator, etc. The signature over the contract packages created by a current owner of the contract blockchain signing the contract package utilizing a private key of a public/private key pair associated with the current owner of the contract blockchain. The or more blockchains may be verified from time to time utilizing industry-standard mining approaches and are applicable to both proof of work, proof of stake, and other hybrid mining techniques.

FIG. 8K is a logic diagram of an embodiment of a method for modifying an exchange item in an exchange item marketplace network. In particular, a method is presented for use in conjunction with one or more functions and features described in conjunction with FIGS. 1-7E, 8A-J, and also FIG. 8K. The method includes step 1000 where a processing module of a server (e.g., a marketplace server of a communication system) records conditions for a plurality of exchange items. For an exchange item of the plurality of exchange items, where the exchange item has a quantifiable value, a serial number, and a current owner, the method continues at step 1002 where the processing module determines whether a corresponding condition of the exchange item is compliant with one or more rules of an applicable set of rules. The determining may include determining a specific use as the one or more rules of the applicable rule set. The determining may further include determining a specific time frame as the one or more rules of the applicable rule set. The determining may yet further include utilizing a sliding scale of compliance based on one or more of a user profile, an exchange item information, exchange item issuer, limited exchange item use, and timing of use. The determining may still further include updating the applicable set of rules based on one or more of a rule changing, a rule expiring, and a new rule being added to the set. For example, updating the rules and utilizing the updated rules for a compliance determination.

When the corresponding condition of the exchange item is compliant with the one or more rules, the method continues at step 1004 where the processing module establishes a secure communication with a computing device affiliated with the current owner to take control of the exchange item. For example, the processing module accesses a contract blockchain currently possessed by the computing device.

While having control over the exchange item, the method continues at step 1006 where the processing module securely modifies the quantifiable value of the exchange item based on the one or more rules to produce a modified exchange item. The modifying may include modifying the quantifiable value by increasing the quantifiable value for the specific use when the specific use is utilized as the one or more rules of the applicable rule set and securely modifying the quantifiable value of the exchange item in accordance with a blockchain protocol (e.g., of the contract blockchain). The modifying may further include sending a notification message to the computing device regarding the increased quantifiable value and the specific use and storing, by the computing device, the exchange item in accordance with the blockchain protocol. The modifying of the quantifiable value may further include increasing the quantifiable value for use during the specific time frame (e.g., an increased discount for the next two hours) when the specific time frame is utilized as the one or more rules of the applicable rule set and sending a notification message to the computing device regarding the increased quantifiable value and the specific time frame. While having control over the exchange item, the processing module prevents the computing device or another computing device from accessing the exchange item (e.g., marking the modified exchange item as not accessible).

The method continues at step 1008 where the processing module releases, via the secure communication, control of the modified exchange item to the computing device affiliated with the current owner. For example, the processing module marks the modified exchange item as accessible enabling use of the modified exchange item by the computing device (e.g., to make a purchase transaction). When the specific time frame expires (e.g., two hours has elapsed), and the modified exchange item was used but did not exhaust the quantifiable value, the method branches to step 1012. When the specific time frame expires and the modified exchange item is unused, the method continues to step 1010.

When the specific time frame expires and the modified exchange item is unused, the method continues at step 1010 where the processing module facilitates producing a reverted EI. The facilitating includes establishing another secure communication with the computing device affiliated to take control of the modified exchange item. While having control over the modified exchange item, the processing module decreases the increased quantifiable value to the quantifiable value to produce a reverted exchange item, prevents the computing device or another computing device from accessing the exchange item, releases, via the other secure communication, control of the reverted exchange item to the computing device affiliated with the current owner, and sends another notification message to the computing device regarding the reverted exchange item. The method branches to step 1014.

When the specific time frame expires, and the modified exchange item was used but did not exhaust the quantifiable value, the method continues at step 1012 where the processing module facilitates producing a further modified EI. The facilitating of producing the further modified EI includes identifying another rule of the applicable set of rules to further modify the modified exchange item and establishing another secure communication with the computing device affiliated to take control of the modified exchange item. While having control over the modified exchange item, the processing module increases a remaining quantifiable value to produce a further modified exchange item, prevents the computing device or another computing device from accessing to the modified exchange item, releases, via the other secure communication, control of the further modified exchange item to the computing device affiliated with the current owner, and sends another notification message to the computing device regarding the further modified exchange item.

The method continues at 1014 where the computing device sends a use request to another server regarding the modified exchange item (e.g., to utilize the modified exchange item for a purchase transaction). The method continues at step 1016 where the other server sends a use notification to the other server (e.g., including information with regards to the purchase transaction). The method continues at step 1018 where the processing module of the server establishes a second secure communication with the computing device affiliated with the current owner to take control of the modified exchange item.

While having control over the exchange item, the method continues at step 1020 where the processing module of the server securely adjusts the quantifiable value of the exchange item based on the use notification to produce an adjusted exchange item (e.g., decrements a remaining balance by an amount of the purchase transaction). The adjusting may further include preventing the computing device, the other server, or other computing devices from accessing the exchange item during the adjusting. The method continues at step 1022 where the processing module of the server, and via the second secure communication, releases control of the adjusted exchange item to the computing device affiliated with the current owner.

The method described above in conjunction with the processing can alternatively be performed by other modules of the exchange item marketplace network or by other devices. In addition, at least one memory section (e.g., a computer readable memory, a non-transitory computer readable storage medium organized into a first memory section, a second memory section, a third memory section, a fourth memory section, etc.) that stores operational instructions can, when executed by one or more processing modules of one or more computing devices (e.g., one or more servers) of the exchange item marketplace network, cause the one or more computing devices to perform any or all of the method steps described above.

FIG. 8L is a schematic block diagram of another embodiment of an exchange item marketplace network (e.g., a data communication system) that includes the initial owner computing device 928 FIG. 6, the exchange item (EI) issuing server 920 of FIG. 6, the EI trusted module 922 of FIG. 6, the merchant server 924 of FIG. 6, marketplace server 18 FIG. 6, the marketplace database 20 of FIG. 6, and the EI buyer computing device 926 FIG. 6. Entities of the exchange item marketplace network may be operably coupled to each other via the network 24 of FIG. 6 or may be directly coupled. The initial owner computing device 928 includes the digital wallet 946 of FIG. 6 and the EI buyer computing device 926 includes the digital wallet 944 of FIG. 6. The marketplace server 18 includes the set up processing 936, the sale processing 938, the use processing 940, and the rule processing 942 all of FIG. 6. The exchange item marketplace network functions to transfer secure custody of an exchange item between entities in accordance with a secure custody protocol. The secure custody protocol includes utilizing one or more of a contract blockchain and a transaction blockchain as previously discussed.

In an example of operation of the transferring the secure custody of the exchange item between entities, the marketplace server 18 (e.g., the server) establishes an initial validity of the exchange item that includes data regarding a quantifiable value, a serial number, and issuance information, where the initial validity authenticates the exchange item and the data. The issuance information includes one or more of issuer identity, and issuance date, and expiration time frame, EI rules, and use parameters. The establishing may include receiving a plurality of exchange items from the EI issuing server 920, where the plurality of exchange items includes the exchange item, and establishing the initial validity of the exchange item with the EI issuing server 920. For example, the set up processing 936 receives EI information 950 and an EI rule set 952 from the EI issuing server 920, where the EI issuing server 920 issues trust information 954 (e.g., a first contract block of the contract blockchain) to the EI trusted module 922 while generating the EI information 950 and the EI rule set 952. Having received the EI information 950 and the EI rule set 952, the set up processing 936 exchanges set up verification 956 with the EI trusted module 922 to validate the EI information 950 and the EI rule set 952.

Having established the initial validity of the exchange item, the marketplace server 18 executes a secure custody protocol to establish that the initial owner computing device 928 (e.g., a first computing device) of the exchange item marketplace network (e.g., data communication system) has secure custody of the exchange item and to maintain validity of the exchange item. The secure custody protocol may further include one or more of a chain of custody mechanism (e.g., the blockchains), exchange item modification restrictions for computing devices of the data communication system (e.g., the initial owner computing device 928, the EI buyer computing device 926, the merchant server 924), and exchange item modification rights for servers of the data communication system. For example, the sale processing 938 exchanges set up information 958 with the initial owner computing device 928 (e.g., a request to purchase the exchange item, confirmation of sale, the EI info 950, one or more of the transaction blockchain and the contract blockchain).

Having executed the secure custody protocol, in response to an exchange item transfer and in accordance with the secure custody protocol, the marketplace server 18 facilitates transfer of the secure custody of the exchange item from the first computing device (e.g., the initial owner computing device 928) to the server or to a second computing device (e.g., the EI buyer computing device 926) of the data communication system. Such transfer supports one or more of a sale of the exchange item, use of the exchange item for a purchase transaction with a merchant associated with the merchant server 924, and modification of the exchange item in accordance with the EI rule set 952.

The transferring the secure custody of the exchange item from the initial owner computing device 928 to the EI buyer computing device 926 includes creating, by the sale processing 938, an offer for sale digital file for the exchange item in response to an offer for sale request from the initial owner computing device 928 and writing the offer for sale digital file for the exchange item to the marketplace database 20 (e.g., a virtual marketplace database) that includes a user interface for computing devices of the data communication system to view offer for sale digital files for a plurality of exchange items. The transferring further includes the sale processing 938 receiving purchase information 970 that includes a request to purchase the exchange item from the EI buyer computing device 926 and upon successful execution of the purchase, transferring the secure custody of the exchange item to the EI buyer computing device 926. For example, the sale processing 938 exchanges sale verification 968 with the EI trusted module 922 to update the transaction blockchain to indicate that the EI buyer computing device 926 is purchasing the exchange item from the initial owner computing device 928.

The transferring the secure custody of the exchange item from the first computing device to the second computing device may further include the sale processing 938 transferring, in response to another exchange item transfer and in accordance with the secure custody protocol, the secure custody of the exchange item from the second computing device to the marketplace server 18 or to a third computing device of the data communication system. The transferring the secure custody of the exchange item from the first computing device to the second computing device may still further include the initial owner computing device 928 sending a request to use the exchange item to the use processing 940 of the marketplace server 18, where the request to use the exchange item identifies the second computing device. When the use is authorized (e.g., the use processing 940 verifies that such use is authorized in accordance with the EI rule set 952), the use processing 940 transfers the secure custody of the exchange item to the second computing device for the second computing device to execute the use, where the second computing device changes the quantifiable value of the exchange item to produce a use modified exchange item (e.g., modified EI info 1030), and the use processing 940 transfers secure custody of the use modified EI info 1030 from the second computing device to the first computing device.

When transferring the secure custody of the exchange item from the initial owner computing device 928 (e.g., the first computing device) to the EI buyer computing device 926 (e.g., the second computing device), the rule processing 942 of the marketplace server 18 determines whether a change to the data of the exchange item occurred while the exchange item is in the secure custody of the second computer. For example, the rule processing 942 indicates the change to the data when the use processing 940 receives merchant use information 980 from the merchant server 924 in response to the EI buyer computer device 926 issuing buyer use information 976 to the use processing 940 to facilitate the purchase transaction with the merchant server 924.

When the change to the data of the exchange item occurred while the exchange item is in the secure custody of the second computer, the use processing 940 of the marketplace server 18 determines whether the exchange item is exhausted (e.g., a remaining balance of zero). When the exchange item is exhausted, the use processing 940 retires the exchange item (e.g., removes the exchange item from the marketplace database 20 and/or issues retirement information to a current owner of exchange item.

When the exchange item is in the secure custody of the server, the rule processing 942 of the marketplace server 18 may modify the data of the exchange item to produce a modified exchange item. The modifying of the data of the exchange item includes identifying a set of rules regarding the exchange item, where the set of rules includes one or more rules, where a rule of the set of rules includes an amount of data change and one or more conditions on when to apply the amount of change. The modifying further includes the rule processing 942 determining that a condition involving the first computing device conforms to the one or more conditions and when the condition involving the first computing device conforms to the one or more conditions, the rule processing 942 modifies the data of the exchange item in accordance with the amount of change (e.g., updates the marketplace database 20). Having modified the data of the exchange item, the rule processing 942 transfers secure custody of the modified exchange item to the initial owner computing device 928 device in accordance with the secure custody protocol.

FIG. 8M is a logic diagram of an embodiment of another method for modifying an exchange item in an exchange item marketplace network. In particular, a method is presented for use in conjunction with one or more functions and features described in conjunction with FIGS. 1-7E, 8A-L, and also FIG. 8M. The method includes step 1100 where a processing module of a server (e.g., a marketplace server of a communication system) establishes an initial validity of an exchange item that includes data regarding a quantifiable value, a serial number, and issuance information, where the initial validity authenticates the exchange item and the data. The establishing may include receiving a plurality of exchange items from an issuing server, where the plurality of exchange items includes the exchange item, and establishing the initial validity of an exchange item with the issuing server.

The method continues at step 1102 where the processing module executes a secure custody protocol to establish that a first computing device of the data communication system has secure custody of the exchange item and to maintain validity of the exchange item. For example, the processing module generates a secure transaction block of a transaction blockchain, where the secure transaction block indicates that the first computing device has secure custody.

The method continues to step 1104 where the processing module transfers, in response to an exchange item transfer and in accordance with the secure custody protocol, the secure custody of the exchange item from the first computing device to the server or to a second computing device of the data communication system (e.g., for a sale, a purchase, or a modification). The method branches to step 1112 when transferring to the server. When transferring to the second computing device, the transferring the secure custody of the exchange item from the first computing device to the second computing device includes creating an offer for sale digital file for the exchange item in response to an offer for sale request from the first computing device the offer for sale digital file for the exchange item to a virtual marketplace database that includes a user interface for computing devices of the data communication system to view offer for sale digital files for a plurality of exchange items, receiving a request to purchase the exchange item from the second computing device, and upon successful execution of the purchase, transferring the secure custody of the exchange item to the second computing device.

The transferring the secure custody of the exchange item from the first computing device to the second computing device may further include transferring, in response to another exchange item transfer and in accordance with the secure custody protocol, the secure custody of the exchange item from the second computing device to the server or to a third computing device of the data communication system. The transferring the secure custody of the exchange item from the first computing device to the second computing device may still further include sending, by the first computing device, a request to use the exchange item to the server, where the request to use the exchange item identifies the second computing device. When the use is authorized, processing module transfers the secure custody of the exchange item to the second computing device for the second computing device to execute the use, where the second computing device changes the quantifiable value of the exchange item to produce a use modified exchange item, and transfers secure custody of the use modified exchange item from the second computing device to the first computing device.

When transferring the secure custody of the exchange item from the first computing device to the second computing device, the method continues at step 1106 where the processing module determines whether a change to the data of the exchange item occurred while the exchange item is in the secure custody of the second computing device (e.g., a lowering of a remaining balance based on usage of the exchange item). When the change to the data of the exchange item occurred while the exchange item is in the secure custody of the second computing device, the method continues at step 1108 where the processing module determines whether the exchange item is exhausted (e.g., remaining balance has reached zero). When the exchange item is exhausted, the method continues at step 1110 where the processing module retires the exchange item.

When the exchange item is in the secure custody of the server, the method continues at step 1112 or the processing module modifies the data of the exchange item to produce a modified exchange item. The modifying the data of the exchange item includes identifying a set of rules regarding the exchange item, where the set of rules includes one or more rules, where a rule of the set of rules includes an amount of data change and one or more conditions on when to apply the amount of change, determining that a condition involving the first computing device conforms to the one or more conditions, and when the condition involving the first computing device conforms to the one or more conditions, modifying the data of the exchange item in accordance with the amount of change. The method continues at step 1114 where the processing module transfers secure custody of the modified exchange item to the first computing device in accordance with the secure custody protocol.

The method described above in conjunction with the processing can alternatively be performed by other modules of the exchange item marketplace network or by other devices. In addition, at least one memory section (e.g., a computer readable memory, a non-transitory computer readable storage medium organized into a first memory section, a second memory section, a third memory section, a fourth memory section, a fifth memory section etc.) that stores operational instructions can, when executed by one or more processing modules of one or more computing devices (e.g., one or more servers) of the exchange item marketplace network, cause the one or more computing devices to perform any or all of the method steps described above.

FIG. 8N is a schematic block diagram of another embodiment of an exchange item marketplace network (e.g., a data communication system, a network-based virtual exchange item marketplace) that includes the network 24 of FIG. 6, the merchant server 924 of FIG. 6, an enterprise storage 1122, an enterprise server 1124, a trusted issuing server 1134, and a plurality of computing devices 1-C. The trusted issuing server 1134 may be implemented utilizing one or more of a secure server, the exchange item (EI) issuing server 920 of FIG. 6, and the EI trusted module 922 of FIG. 6. The enterprise storage 1122 may be implemented utilizing a plurality of storage servers at a local or distributed level for storing large amounts of data. For example, the enterprise storage 1122 may be implemented utilizing the marketplace database 20 of FIG. 6. The enterprise server 1124 may be implemented utilizing one or more servers for processing large amounts of data. For example, the enterprise server 1124 may be implemented utilizing the marketplace server 18 of FIG. 6. The plurality of computing devices may include one or more of the initial owner computing device 928 of FIG. 6, the EI buyer computing device 926 of FIG. 6, and any other computer that is part of the data communication system.

The enterprise storage 1122 includes one or more of the agreement database 930 of FIG. 6, the user database 932 of FIG. 6, the exchange item database 934 of FIG. 6, and a rules database 1120. The enterprise server 1124 includes a network interface, a memory, and a processing module operably coupled to the network interface into the memory. The network interface may be implemented utilizing the network interface module(s) 78 of FIG. 3. The memory may be implemented utilizing one or more of the main memory 66 of FIG. 3, the memory interface module(s) 80 of FIG. 3, the flash memory 92 of FIG. 3, the HD memory 94 of FIG. 3, the SS memory 96 of FIG. 3, and the cloud memory 98 of FIG. 3. The processing module may be implemented utilizing the processing module 62 of FIG. 3 and may be utilized to implement one or more of a set up module 1126, a sale module 1128, a use module 1130, and a rule application module 1132.

The set up module 1126 functions to initially validate exchange items and create records in the exchange item database 934 for validated exchange items, where each of the exchange items includes data regarding a quantifiable value, a serial number, and issuance information. The sale module 1128 functions to securely transfer a selected exchange item from the first computing device to the second computing device. The use module 1130 functions to securely apply the selected exchange item to a closed loop digital transaction in accordance with an agreement of the agreements database 930. The rule application module 1132 functions to securely modify the data of the selected exchange item in accordance with an applicable set of rules from the rules database 1120. Examples of operation of the enterprise server 1124 are discussed in greater detail below.

The enterprise storage 1122 further functions to store the user database 932, where the user database 932 includes one or more of a user identifier field (e.g., identified person and associated computing devices), an exchange item buying information field; (e.g., which EIs the user buys), and exchange item use information field (e.g., how much, how often, and what types of EIs the user uses), and an exchange item selling information field.

To facilitate offering exchange items for sale, the processing module of the enterprise server 1124 accesses a record in the user database 932 of a user associated with a computing device, accesses one or more of the exchange item database, the agreements database, and the rules database to identify one or more exchange items of interest to the user, and sends, via the network interface, a message to the computing device regarding the one or more exchange items of interest.

When acquiring an exchange item, the computing device of the plurality of computing devices stores a user exchange item database (e.g., a portion of the exchange item database 934 that is pertinent to the user and computing device) that includes one or more of an exchange item identifier field, an issuer identifier field, an exchange item information field, a use options field, a control field, a location field, a status field, and a transaction field. The exchange item database 934 includes one or more records, where each record includes one or more of an exchange item identifier field, an issuer identifier field, a current owner identifier field, an exchange item information field (e.g., value, type, issuance date, expiration date, use parameters), a conditions field (e.g., tracks conditions of an owner regarding potential applicability of rules), a rules identifier field (e.g., identifies one or more applicable rule sets), an offer for sale field (e.g., an indication that current owner is offering the EI for sale, doesn't prohibit current owner from using EI), a use options field (e.g., identifies which merchants will accept the EI as a form of payment, this is determined based on content of the agreement database 930), a control field (e.g., identifies the entity that currently has the right to use or modify the EI), a location field (e.g., identifies the entity that currently has physical possession of the EI, which may be different than the entity that has control, for example, the server may have physical possession and a computing device may have control), a status field (e.g., identify the status of the EI such as active, inactive, valid, questionable validity, exhausted, expired, etc.), and a transaction field (e.g., a record of the transaction history of the EI, built into blockchain). Each field may include sub-fields to accommodate various pieces of information being recorded.

The agreements database includes one or more of an issuer identifier field, an exchange item type field (e.g., identifies the types of EI that are part of the agreement), a recipient entity identifier field (e.g., identifies the entities that will accept the EI as a form of payment), an agreement identifier field (e.g., agreement between issuer and recipient entity on use of EI), and a rules identifier field (e.g., if rules exist for EI, do they apply for use with the recipient, may vary from recipient to recipient). The rules database includes one or more of an issuer identifier field, an exchange item type field (e.g., per issuer), a rule set field (e.g., includes rules for a set of rules: discount, conditions to be met, etc.), and a rules applicability field (e.g., for an EI type, does the rule set apply or not).

When adding a new exchange item to the data communication system, the set up module 1126 establishes establish, via the network interface and the network 24, a secure communication link with the trusted issuing server 1134, where the issuing server 1134 performs one or more of creating the EI to put directly into the exchange item database, providing on-the-fly creation at request of a user or merchant, providing the EI as a location based promotion, and providing the EI as a user based promotion, etc. Having established the link, the set up module 1126 receives, via the network interface and the network 24, the data of the exchange item from the trusted issuing server 1134 in accordance with a secure custody protocol (e.g., utilizing a contract blockchain). Having received the data, the set up module 1126 establishes the enterprise server 1124 as having secure custody of the exchange item (e.g., as a current owner as noted within the contract blockchain). Having established the secure custody, the set up module 1126 creates a record in the exchange item database 934 for the exchange item.

When the exchange item is to be sold to a computing device, the sale module 1128 receives, via the network interface and the network 24, a request to sell a particular exchange item for a first computing device (e.g., computing device 1). Having received the request, the sale module 1128 verifies that the first computing device has secure custody of the particular exchange item in accordance with the secure custody protocol (e.g., verifies a signature of the computing device 1). When the first computing device has secure custody of the particular exchange item, the sale module 1128 verifies the data of the exchange item (e.g., verifies with the trusted issuing server 1134, verifies with the exchange item database 934, verifies a signature over the data). When the data of the exchange item is verified, the sale module 1128 adds an offer for sale digital record for the particular exchange item in the network-based virtual exchange item marketplace (e.g., indicates for sale in the exchange item database 934).

When the exchange item is to be sold from the first computing device to the second computing device, the sale module 1128 receives, via the network interface and the network 24, a request to purchase a particular exchange item from the second computing device (e.g., computing device 2) and authenticates the second computing device. When the second computing device is authenticated, the sale module 1128 transfers secure custody of the particular exchange item from the first computing device to the second computing device in accordance with the secure custody protocol (e.g., facilitates modification of the contract blockchain to indicate that the computing device 2 is the new owner), and removes the offer for sale digital record for the particular exchange item from the network-based virtual exchange item marketplace (e.g., updates the exchange item database 934).

When a computing device (e.g., computing device 2) utilizes an exchange item in a purchase transaction (e.g., a closed loop digital transaction), the use module 1130 receives, via the network interface and the network 24 from a computing device, a request to use the exchange item in a particular closed loop digital transaction with a recipient entity server (e.g., the merchant server 924). Having received the request, the use module 1130 accesses the agreements database 930 to determine whether an agreement exists between an issuing server (e.g., the trusted issuing server 1134) of the particular exchange item and the recipient entity server. When the agreement exists, the use module 1130 determines whether the particular closed loop digital transaction is in accordance with the agreement (e.g., user is allowed, the particular type of transaction is allowed, rules and conditions apply, etc.). When the particular closed loop digital transaction is in accordance with the agreement, the use module 1130 authorizes the particular closed loop transaction. When the agreement does not exist or the particular closed loop digital transaction is not in accordance with the agreement, use module 1130 denies the particular closed loop transaction.

From time to time, the rule application module 1132 considers modifying the data of the exchange item (e.g., based on one or more of interpreting a schedule, receiving a request, detecting a change in a condition). When considering the modifying of the data, the rule application module 1132 obtains condition information of a computing device having secure custody of a particular exchange item (e.g., condition from user profile and history provides the condition information, physical location, environmental conditions, etc.). The obtaining includes one or more of identifying a condition source, interpreting condition data from the identified condition source, receiving the condition information, performing a lookup, and generating the condition information based on condition data.

Having obtained the condition information, the rule application module 1132 accesses rules of the applicable set of rules associated with the particular exchange item from the rules database 1120. Having accessed the rules, the rule application module 1132 compares the condition information with the rules of the applicable set of rules. When the condition information compares favorably with the rules of the applicable set of rules, the rule application module 1132 obtains secure custody of the particular exchange item from the computing device in accordance with the secure custody protocol (e.g., physically take custody by a data transfer or update the exchange item database 934 to indicate that the enterprise server 1124 has secure custody). While having secure custody, the rule application module 1132 modifies the data of the particular exchange item in accordance with the rules of the application set of rules to produce a modified exchange item and transfers secure custody of the modified exchange item to the computing device.

FIG. 8P is a logic diagram of an embodiment of another method for securely processing an exchange item in an exchange item marketplace network. In particular, a method is presented for use in conjunction with one or more functions and features described in conjunction with FIGS. 1-7E, 8A-N, and also FIG. 8P. The method includes step 1140 where a processing module (e.g., of an enterprise server of a data communication system) stores an exchange item database, an agreements database, and a rules database in an enterprise storage. The storing may further include storing a user database in the enterprise storage and accessing a record in the user database of a user associated with a computing device of a plurality of computing devices. The storing may yet further include accessing a record in the user database of a user associated with a computing device, accessing one or more of the exchange item database, the agreements database, and the rules database to identify one or more exchange items of interest to the user, and sending a message to the computing device regarding the one or more exchange items of interest. The storing may still further include storing, by the computing device of the plurality of computing devices, a user exchange item database (e.g., a portion of the user database).

The method continues at step 1142 where the processing module initially validates exchange items and creates records in the exchange item database for validated exchange items, where each of the exchange items includes data regarding a quantifiable value, a serial number, and issuance information. The initially validating the exchange items and creating records in the exchange further includes establishing a secure communication link with a trusted issuing server, receiving the data of an exchange item from the issuing server in accordance with a secure custody protocol, establishing the enterprise server as having secure custody of the exchange item, and creating a record in the exchange item database for the exchange item.

The method continues to step 1144 where the processing module securely transfers a selected exchange item from a first computing device to a second computing device in accordance with an offer for sale of the selected exchange item. The secure transferring of the selected exchange item from the first computing device to the second computing device in accordance with the offer for sale of the selected exchange item further includes a variety of approaches. In a first approach, the processing module receives a request to sell the selected exchange item from the first computing device, and verifies that the first computing device has secure custody of the particular exchange item in accordance with a secure custody protocol. When the first computing device has secure custody of the particular exchange item, the processing module verifies the data of the exchange item. When the data of the exchange item is verified, the processing module adds an offer for sale digital record for the particular exchange item in a network-based virtual exchange item marketplace (e.g., an exchange item database).

In a second approach to the securely transferring the selected exchange item from the first computing device to the second computing device in accordance with the offer for sale of the selected exchange item, the processing module receives a request to purchase a particular exchange item from the second computing device, and authenticates the second computing device. When the second computing device is authenticated, the processing module transfers secure custody of the particular exchange item from a first computing device to the second computing device in accordance with a secure custody protocol and removes an offer for sale digital record for the particular exchange item from the network-based virtual exchange item marketplace (e.g., from the exchange item database).

The method continues at step 1146 where the processing module securely applies the selected exchange item to a closed loop digital transaction between two computing entities (e.g., computing device or server) in accordance with an agreement of the agreements database. The securely applying the selected exchange item to the closed loop digital transaction further includes receiving, from a computing device, a request to use an exchange item in a particular closed loop digital transaction with a recipient entity server, and accessing the agreements database to determine whether an agreement exists between an issuing server of the particular exchange item and the recipient entity server. When the agreement exists, the processing module determines whether the particular closed loop digital transaction is in accordance with the agreement. When the particular closed loop digital transaction is in accordance with the agreement, the processing module authorizes the particular closed loop transaction. When the agreement does not exist or the particular closed loop digital transaction is not in accordance with the agreement, the processing module denies the particular closed loop transaction.

The method continues at step 1148 where the processing module securely modifies the data of the selected exchange item in accordance with an applicable set of rules from the rules database. The securely modifying of the data of the selected exchange item further includes obtaining condition information of a computing device having secure custody of a particular exchange item, accessing rules of the applicable set of rules associated with the particular exchange item from the rules database, and comparing the condition information with the rules of the applicable set of rules. When the condition information compares favorably with the rules of the applicable set of rules, the processing module obtains secure custody of the particular exchange item from the computing device in accordance with secure custody protocol. While having secure custody, the processing module modifies the data of the particular exchange item in accordance with the rules of the application set of rules to produce a modified exchange item and transfers secure custody of the modified exchange item to the computing device.

The method described above in conjunction with the processing can alternatively be performed by other modules of the exchange item marketplace network or by other devices. In addition, at least one memory section (e.g., a computer readable memory, a non-transitory computer readable storage medium organized into a first memory section, a second memory section, a third memory section, a fourth memory section, a fifth memory section etc.) that stores operational instructions can, when executed by one or more processing modules of one or more computing devices (e.g., one or more servers) of the exchange item marketplace network, cause the one or more computing devices to perform any or all of the method steps described above.

FIGS. 9A and 9B are schematic block diagrams of another embodiment of an exchange item marketplace network that includes exchange item (EI) issuing servers 1-2, the EI trusted module 922 of FIG. 6, the EI buyer computing device 926 of FIG. 6, the point-of-sale (POS) equipment 32 of FIG. 1, the merchant server 924 of FIG. 6, the marketplace server 18 of FIG. 6, and the marketplace database 20 of FIG. 6. The EI issuing servers 1-2 may be implemented utilizing the EI issuing server 920 of FIG. 6. Hereafter, the EI issuing server 1 may be interchangeably referred to as a first issuing server and the EI issuing server 2 may be interchangeably referred to as a second issuing server. Hereafter, the EI buyer computing device 926 may be interchangeably referred to as a user computing device. The marketplace server 18 includes the set up processing 936 of FIG. 6, the use processing 940 of FIG. 6, and the rule processing 942 of FIG. 6. Hereafter the exchange item marketplace network may be interchangeable referred to as a data communication system. The data communication system functions to facilitate redeeming of a cross-brand exchange item of the exchange item marketplace network.

FIG. 9A illustrates an example of the facilitating of the redeeming of the cross-brand exchange item where the EI issuing server 1 (e.g., the first issuing server), and the EI issuing server 2 (e.g., the second issuing server) establish an agreement between regarding first exchange items to have an extended use corresponding to a second type of use (e.g., may or may not be same level of use), where the first issuing server issues the first exchange items that are restricted to a first type of use (e.g., use only with first issuing server, use for only a first type of product, use for products by a particular manufacturer) and where the second issuing server issues second exchange items that are restricted to the second type of use (e.g., use only with second issuing server, use for only a second type of product, use for products by another particular manufacturer). For example, the EI issuing servers 1-2 exchange agreement information 1150 to establish the agreement, where the agreement includes one or more of allowing redemption of a first exchange item for the second type of use (e.g., using an exchange item associated with the EI issuing server 1 for purchase of a product associated with the EI issuing server 2) and allowing redemption of a second exchange item for the first type of use (e.g., using an exchange item associated with the EI issuing server 2 for purchase of a product associated with the EI issuing server 1). The exchange agreement information 1150 includes one or more of brand identifiers of a cross-brand utilization agreement rule, utilization restrictions, and exchange item serial number, and an exchange item identifier.

Subsequent to the establishment of the agreement, the set up processing 936 (e.g., a processing module of one or more processing modules of the marketplace server 18) stores the agreement regarding the extended use of the first exchange items. For example, the set up processing 936 receives one or more of the agreement information 1150, EI information 950, and an EI rule set 952 from the EI issuing server 1, and generates a new exchange item associated with a first brand of the EI issuing server 1, where a rule of the EI rule set 952 associated with the new exchange item enables redemption of the exchange item via a merchant associated with a second brand, where the first brand of the second brand have established the agreement, and where the EI issuing server 1 and the EI trusted module 922 exchange trust information 954, and where the EI trusted module 922 exchanges set up verification 956 with the set up processing 936 to verify the new exchange item. Having generated the new exchange item, the set up processing 936 stores one or more of the agreement information 1150, the EI info 950, and the EI rule set 952. For example, the set up processing 936 stores the agreement information 1150 in the marketplace database 20. As another example, the set up processing 936 sends the agreement information 1150 to the EI buyer computing device 926 for storage in the digital wallet 944.

Having stored the agreement and the exchange item in the marketplace database 20, the set up processing 936 facilitates transfer of control of the exchange item to the EI buyer computing device 926 in accordance with a secure custody protocol by transferring set up information 958 with the EI buyer computing device 926. The facilitating further includes one or more of receiving a purchase request from the EI buyer computing device 926, exchanging the set up information 958, where the processing of the set up information 958 takes control of the exchange item (i.e., with a private key of the marketplace server 18) and enables control of the exchange item by the EI buyer computing device 926 (i.e., obtaining signature from the EI buyer computing device), and generating a portion of a blockchain ledger to include at least some of the agreement information 1150, the EI information 950, the EI rule set 952, and the set up information 958.

Alternatively, or in addition to, the first and second issuing servers update the agreement to reflect a change to the extended use (e.g., broadening or narrowing brand utilization, product inclusions, special offers, etc.) and the set up processing 936 of the marketplace server 18 stores the updated agreement (e.g., in the marketplace database 20, in the digital wallet 944). Further alternatively, or further in addition to, the first and second issuing servers establish a second agreement between the first issuing server and the second issuing server regarding the second exchange items to have a second extended use corresponding to the first type of use, and the set up processing 936 stores the second agreement regarding the second extended use of the second exchange items (e.g., in the marketplace database 20, in the digital wallet 944 via the EI buyer computing device 926).

FIG. 9B further illustrates the example of the facilitating of the redeeming of the cross-brand exchange item where the use processing 940 of the marketplace server 18 receives a request for use of one of the first exchange items from the merchant server 924 regarding a transaction by the EI buyer computing device 926 (e.g., the user computing device) for a particular item, where the marketplace server generated a data file for the one of the first exchange items, where the data file includes a quantifiable value, a serial number, and issuance information (e.g., issuance information including identity of the first issuing server, issuance date, expiration date, use parameters, exchange item rules, etc.), where the marketplace server receives a request to acquire the one of the first exchange items by the user computing device, and where the marketplace server executes an acquisition process to securely establish ownership of the one of the first exchange items by the user computing device. For example, the use processing 940 receives merchant use information 980 from the merchant server 924, where the merchant server 924 receives buyer use information 976 from the EI buyer computing device 926 via the POS equipment 32, and where the merchant use information 980 indicates a cross-brand redemption request. For instance, the EI buyer computing device 926 interprets a representation of a portion of a blockchain ledger stored in the digital wallet 944 associated with exchange item and interprets an exchange item rule indicating cross-brand redemption is enabled.

Having received the merchant use information 980, the use processing 940 and/or the rule processing 942 verifies the cross-brand redemption request (e.g., verifies that an exchange item rule enables cross-brand redemption). Having verify the cross-brand redemption request, the use processing 940 of the marketplace server 18 determines whether the merchant server 924 is affiliated with the first or second issuing server. For example, the use processing 940 interprets a brand affiliation indicator of the merchant use information 980 and indicates that the merchant server 924 is affiliated with the EI issuing server 2 when the merchant use information 980 indicates a brand identity associated with the EI issuing server 2 and not associated with the EI issuing server 1 (e.g., cross-brand redemption scenario).

When the merchant server 924 is affiliated with the second issuing server, the use processing 940 interprets the agreement to determine extended use parameters of the one of the first exchange items with the merchant server regarding the particular item. For example, the merchant server 924 recovers the agreement information 1150 from the marketplace database 20 and verifies that received the agreement information via the merchant use information 980 is substantially the same (e.g., to enable cross-brand utilization). Having interpreted the agreement, the use processing 940 processes, in accordance with the extended use parameters, use of the one of the first exchange items between the EI buyer computing device 926 and the merchant server 924 regarding the particular item. For example, the use processing 940 sends the merchant use information 980 to the EI issuing server 2 and receives payment information 1152 for transmission to the merchant server 924, where the payment information 1152 accommodates the redemption of the one of the first exchange items. In addition, the EI issuing server 2 may exchange further agreement information 1150 that indicates one or more of a required payment from the EI issuing server number 1 (e.g., that received an initial payment for the exchange item from the EI buyer computing device 926) a credit due to the EI issuing server 2 which may offset utilization of exchange items associated with the EI issuing server 2 at another merchant server associated with the EI issuing server 1 (e.g., a reverse cross-brand utilization).

When the merchant server 924 is affiliated with the first issuing server (e.g., a first brand), the use processing 940 obtains a first agreement regarding the first type of use (e.g., interprets a portion of recovered agreement information 1150 from the marketplace database 20). Having obtained the first agreement, the use processing 940 processes, in accordance with the first type of use, use of the one of the first exchange items between the EI buyer computing device 926 and the merchant server 924 regarding the particular item. For example, the use processing 940 processes the request as a same-brand request. For instance, the use processing 940 deducts a payment amount associated with the request from an available balance of the exchange item (e.g., as recorded in the marketplace database 20, as indicated in a blockchain ledger from the digital wallet 944).

When the merchant server is not affiliated with the first or the second issuing server, the use processing 940 denies the use of the one of the first exchange items between the EI buyer computing device 926 and the merchant server 924 regarding the particular item. Alternatively, when the merchant server is not affiliated with the first or the second issuing server, the use processing 940 identifies an available exchange item having use restrictions that allow the use between the user computing device and the merchant server regarding the particular item, sends an offer to acquire the available exchange item to the EI buyer computing device 926, receives a request to acquire the available exchange item by the EI buyer computing device 926, and executes an acquisition process to securely establish ownership of the available exchange items by the user computing device (e.g., for subsequent immediate utilization).

The establishment of an agreement may further include establishing, by the first issuing server, a first agreement regarding the first type of use of the first exchange items, where the first type of use includes, but is not limited to, use of a first exchange item with merchant servers affiliated with a first type of merchant, use of the first exchange item for a first type of product or server, use the first exchange item for products or services from a first particular manufacturer; storing, by the market place server, the first agreement; updating, by the first issuing server, the first agreement to include limited time use offers for the first exchange items to produce an updated first agreement; and storing, by the market place server, the updated first agreement. The establishment of the agreement may still further include establishing, by the second issuing server, a second agreement regarding the second type of use of the second exchange items, where the second type of use includes, but is not limited to, use of a second exchange item with merchant servers affiliated with a second type of merchant, use of the second exchange item for a second type of product or server, use the second exchange item for products or services from a second particular manufacturer; storing, by the market place server, the second agreement; updating, by the second issuing server, the second agreement to include limited time use offers for the second exchange items to produce an updated second agreement; and storing, by the market place server, the updated second agreement.

FIG. 9C is a logic diagram of an embodiment of a method for redeeming a cross-brand exchange item in an exchange item marketplace network. In particular, a method is presented for use in conjunction with one or more functions and features described in conjunction with FIGS. 1-8P, 9A-B, and also FIG. 9C. The method includes step 1170 where a first issuing server and a second issuing server (e.g., of an exchange item marketplace network) establish an agreement regarding first exchange items to have an extended use corresponding to a second type of use (e.g., cross-brand), where the first issuing server issues the first exchange items that are restricted to a first type of use (e.g., redemption at a merchant affiliated with a brand of the first issuing server) and wherein the second issuing server issues second exchange items that are restricted to the second type of use (e.g., redemption at another merchant affiliated with a brand of the second issuing server).

The method continues at step 1172 where a processing module of a marketplace server stores the agreement regarding the extended use of the first exchange items. Alternatively, or in addition to, the first and second issuing servers update to reflect a change to the extended use and the processing module stores the updated agreement. As another alternative, the first issuing server and the second issuing server establish a second agreement regarding the second exchange items to have a second extended use corresponding to the first type of use and the processing module stores the second agreement regarding the second extended use of the second exchange items.

The method continues at step 1174 where the processing module receives a request for use of one of the first exchange items from a merchant server regarding a transaction by a user computing device for a particular item, where the processing module generates a data file for the one of the first exchange items, where the data file includes a quantifiable value, a serial number, and issuance information, where the processing module receives a request to acquire the one of the first exchange items by the user computing device, and where the processing module executes an acquisition process to securely establish ownership of the one of the first exchange items by the user computing device.

The method continues at step 1176 where the processing module determines whether the merchant server (e.g., of the processing module) is affiliated with the first or second issuing server (e.g., identifying a brand associated with the request for use). The method branches to step 1182 when the merchant server is affiliated with the first issuing server. The method branches to step 1186 when the merchant server is unaffiliated with the first and second issuing servers and restricted use is not allowed (e.g., use of another exchange item to support the request is not allowed). The method branches to step 1188 when the merchant server is unaffiliated with the first and second issuing servers and restricted use is allowed. The method continues to step 1178 when the merchant server is affiliated with the second issuing server (e.g., cross-brand use).

When the merchant server is affiliated with the second issuing server, the method continues at step 1178 where the processing module interprets the agreement to determine extended use parameters of the one of the first exchange items with the merchant server regarding the particular item. The method continues at step 1180 where the processing module, in accordance with the extended use parameters (e.g., cross-brand), processes use of the one of the first exchange items between the user computing device and the merchant server regarding the particular item.

When the merchant server is affiliated with the first issuing server, the method continues at step 1182 where the processing module obtains a first agreement regarding the first type of use. The method continues at step 1184 where the processing module, in accordance with the first type of use, processes use of the one of the first exchange items between the user computing device and the merchant server regarding the particular item.

When the merchant server is not affiliated with the first or the second issuing server and restricted use is not allowed, the method continues at step 1186 where the processing module denies the use of the one of the first exchange items between the user computing device and the merchant server regarding the particular item. When the merchant server is not affiliated with the first or the second issuing server and restricted use is allowed (e.g., in accordance with an exchange item rule), the method continues at step 1188 where the processing module identifies an available exchange item having use restrictions that allow the use between the user computing device and the merchant server regarding the particular item (e.g., searching a marketplace database).

The method continues at step 1190 where the processing module sends an offer to acquire the available exchange item to the user computing device. The method continues at step 1192 where the processing module receives a request to acquire the available exchange item by the user computing device. The method continues at step 1194 where the processing module executes an acquisition process to securely establish ownership of the available exchange item by the user computing device such that the user computing device may utilize the available exchange item to favorably complete the request.

The method to establish an agreement may further include establishing, by the first issuing server, a first agreement regarding the first type of use of the first exchange items, where the first type of use includes, but is not limited to, use of a first exchange item with merchant servers affiliated with a first type of merchant, use of the first exchange item for a first type of product or server, use the first exchange item for products or services from a first particular manufacturer; storing, by the market place server, the first agreement; updating, by the first issuing server, the first agreement to include limited time use offers for the first exchange items to produce an updated first agreement; and storing, by the market place server, the updated first agreement.

The method to establish the agreement may still further include establishing, by the second issuing server, a second agreement regarding the second type of use of the second exchange items, where the second type of use includes, but is not limited to, use of a second exchange item with merchant servers affiliated with a second type of merchant, use of the second exchange item for a second type of product or server, use the second exchange item for products or services from a second particular manufacturer; storing, by the market place server, the second agreement; updating, by the second issuing server, the second agreement to include limited time use offers for the second exchange items to produce an updated second agreement; and storing, by the market place server, the updated second agreement.

The method described above in conjunction with the processing module, the first and second issuing servers, the user computer, and the marketplace server can alternatively be performed by other modules of the exchange item marketplace network or by other devices. In addition, at least one memory section (e.g., a computer readable memory, a non-transitory computer readable storage medium organized into a first memory element, a second memory element, a third memory element, a fourth element section, a fifth memory element etc.) that stores operational instructions can, when executed by one or more processing modules of one or more computing devices (e.g., one or more servers) of the exchange item marketplace network, cause the one or more computing devices to perform any or all of the method steps described above.

FIG. 10A is a schematic block diagram of another embodiment of an exchange item marketplace network that includes the EI issuing server 920 of FIG. 6, the EI trusted module 922 of FIG. 6, the marketplace server 18 of FIG. 6, the marketplace database 20 of FIG. 6, and the initial owner computing device 928 of FIG. 6. The initial owner computing device 928 includes the digital wallet 946 of FIG. 6. The marketplace server 18 includes the set up processing 936 of FIG. 6 and a private key 1210. The exchange item marketplace network functions to anonymously acquire an exchange item.

In an example of operation of the anonymous acquisition of the exchange item, the set up processing 936 generates a new exchange item. The generating includes exchanging EI info 950 and an EI rule set 952 with the EI issuing server 920, where the EI issuing server 920 exchanges trust information 954 with the EI trusted module 922, and where the EI trusted module 922 exchanges set up verification 956 with the set up processing 936 to verify the new exchange item.

Having produced the new exchange item, the set up processing 936 takes control of the new exchange item in accordance with a secure custody protocol. For example, the set up processing 936 utilizes the private key 1210 to sign a portion of a blockchain ledger associated with the new exchange item, where the portion includes a public key of a private/public key pair that includes the private key 1210, and where an EI rule includes authorization for the marketplace server 18 to transfer control of the new EI upon subsequent activation (e.g., for the initial owner computing device 928).

With control of the new exchange item, the set up processing 936 receives set up information 1212 from the initial owner computing device 928, where the set up information 1212 includes a request to associate the new exchange item with the initial owner computing device. The receiving includes the set up processing 936 matching an exchange item identifier of the request with an identifier of the new exchange item (e.g., from the marketplace database 20).

Having received the set up information, the set up processing 936 facilitates transfer of ownership to associate the new exchange item with the initial owner computing device 928. For example, the set up processing 936 generates a new EI rule indicating ownership of the EI by the initial owner computing device, signs the new EI rule utilizing the private key 1210 to produce an updated exchange item, and updates the blockchain ledger to include the updated exchange item for storage in one or more of the digital wallet 946 and the marketplace database 20.

FIG. 10B is a logic diagram of an embodiment of a method for anonymous acquisition of an exchange item in an exchange item marketplace network. The method includes step 1220 where a processing module (e.g., of a marketplace server) generates a new exchange item, where the exchange item is controllable by a marketplace server at least until acquisition by an initial owner computing device. For example, the processing module exchanges EI information and an EI rule set with an EI issuing server and exchanges set up verification with an EI trusted module to verify the new exchange item (e.g., verifies a signature over the EI in accordance with a secure custody protocol).

The method continues at step 1222 where the processing module takes control of the new exchange item in accordance with a secure custody protocol. For example, the processing module utilizes a private key of a private/public key pair to sign a portion of a blockchain ledger associated with the new exchange item, where an EI rule associated with the new EI includes authorization for the processing module to transfer control of the EI upon activation.

The method continues at step 1224 for the processing module receives set up information from the initial owner computing device, where the set up information includes a request to associate the new exchange item with the initial owner computing device. The receiving includes matching an exchange item identifier of the set up information with an identifier of the new exchange item.

The method continues at step 1226 where the processing module facilitates transfer of ownership to associate the new exchange item with the initial owner computing device in accordance with the secure custody protocol. For example, the processing module generates a new EI rule indicating ownership of the new exchange item by the initial owner computing device, utilizes the private key to sign the new EI rule to produce an updated exchange item, and updates the blockchain ledger with the updated exchange item for storage in one or more of a digital wallet associated with the initial owner computing device and a marketplace database.

FIG. 11A is a schematic block diagram of another embodiment of an exchange item marketplace network that includes the EI issuing server 920 of FIG. 6, the EI trusted module 922 of FIG. 6, the marketplace server 18 of FIG. 6, the marketplace database 20 of FIG. 6, EI buyer computing devices 1-2, the point-of-sale (POS) equipment 32 of FIG. 1, and the merchant server 924 of FIG. 6. Each EI buyer computing device may be implemented utilizing the EI buyer computing device 926 of FIG. 6. Each EI buyer computing device 1-2 includes a corresponding digital wallet 1-2, where the digital wallet may be implemented utilizing the digital wallet 944 of FIG. 6. The marketplace server 18 includes the set up processing 936 of FIG. 6, the use processing 940 of FIG. 6, and the rule processing 942 of FIG. 6. The exchange item marketplace network functions to identify unauthorized exchange item (EI) cloning.

In an example of operation of the identifying of the unauthorized exchange item cloning, the set up processing 936 receives a second request to associate a common exchange item with the EI buyer computing device 2, where the common exchange item was previously associated with the EI buyer computing device 1 in response to receiving a first request to associate the common exchange item with the EI buyer computing device 1 (e.g., the set up processing 936 received set up information 958 from the EI buyer computing device 1 with regards to exchange item 457, the set up processing 936 exchanged EI info 950 and EI rule set 952 with the EI issuing server 920, where the EI rule set includes tracking two or more computing device associations with a common EI, where the EI issuing server 920 exchanges trust information 954 with the EI trusted module 922, and where the EI trusted module 922 exchanges set up verification 956 with the set up processing 936).

When receiving the second request for the common exchange item, the rule processing 942 interprets a rule associated with exchange item in regards to enabling associations of the two or more computing devices. The interpreting includes validating a record for the exchange item that includes the rule utilizing a secure custody protocol (i.e., validate a portion of a blockchain ledger), interpreting a rule, and indicating a status of the rule (i.e., allowed/disallowed).

When receiving a request to redeem the common exchange item, the use processing 940 determines whether to allow redeeming of the exchange item by a requesting computing device in accordance with the rule. The determining includes one or more of receiving merchant use information 980 from the merchant server 924, where the merchant server 924 receives buyer use information 976 from the point-of-sale equipment 32, where the point-of-sale equipment 32 receives the buyer use information 976 from the EI buyer computing device 2, obtaining the portion of the blockchain ledger (i.e., from the merchant use info 980, from the marketplace database 20), validating portion, extracting the rule, interpreting a rule, and executing a risk abatement procedure, and indicating whether the requesting computing device is allowed to redeem the exchange item based on the risk abatement procedure output (i.e., comparing an estimated risk level to a maximum risk threshold level). For example, the use processing 940 indicates allowing the redemption request when determining that the EI buyer computing device 2 is the likely owner of the exchange item 457. As another example, the use processing 940 indicates disallowing the redemption request when determining that the EI buyer computing device 1 is the likely owner of the exchange item 457.

FIG. 11B is a logic diagram of an embodiment of a method for identifying unauthorized exchange item cloning in an exchange item marketplace network. The method includes step 1240 where a processing module (e.g., of a marketplace server) receives a second request to associate a common exchange item with a second computing device, where the common exchange item was previously associated with a first computing device. For example, in response to receiving a first request to associate the common exchange item with the first computing device, the processing module receives set up information from the second computing device, where the set up information includes an identifier of the exchange item. The processing module matches an exchange item identifier of the request to an identifier of an exchange item that was previously associated with the first computing device (e.g., as recorded in a marketplace database).

The method continues at step 1242 where the processing module interprets a multiuser EI rule associated with the common exchange item. The trophy includes obtaining a portion of a blockchain ledger that includes the multiuser EI rule associated with the common exchange item, validating the portion in accordance with a secure custody protocol (i.e., validate a signature), interpreting a rule, indicating status of the rule, and when allowed, associating the second computing device to the exchange item. When disallowed, the processing module rejects the second request and sends a security alert to the first computing device.

When receiving a request to redeem the common exchange item, the method continues at step 1244 where the processing module determines whether to allow redeeming of the exchange item by a requesting computing device in accordance with the multiuser EI rule. For example, the processing module receives merchant use information from the merchant server, where the merchant server receives buyer use information from the requesting computing device, obtains the portion of the blockchain ledger, validates the portion, extracts the multiuser EI rule, interprets the multiuser EI rule, executes a risk abatement procedure, and indicates whether the requesting computing device is allowed to redeem the exchange item based on an output from the risk abatement procedure.

FIG. 12A is a schematic block diagram of another embodiment of an exchange item marketplace network that includes EI issuing servers 1-2, the EI trusted module 922 of FIG. 6, the marketplace server 18 of FIG. 6, the marketplace database 20 of FIG. 6, and the EI buyer computing device 926 of FIG. 6. Each EI issuing server 1-2 may be implemented utilizing the EI issuing server 920 of FIG. 6. The EI buyer computing device 926 includes the digital wallet 944 of FIG. 6. The marketplace server 18 includes the set up processing 936 of FIG. 6 and the rule processing 942 of FIG. 6. The exchange item marketplace network functions to modify brand affiliation.

In an example of operation of the modifying of the brand affiliation, the set up processing 936 generates a new exchange item (EI) associated with a first brand, where a swap rule associated with the EI enable swapping of the first brand of the EI to a second brand, and where the first brand and the second brand have established a cross-brand swap agreement. The generating includes one or more of the set up processing 936 exchanging EI info 950 and an EI rule set 952 with the issuing server 1, where the EI rule set 952 includes at least a portion of agreement information 1150, where the agreement information 1150 is exchanged between the EI issuing server 1 and the EI issuing server 2, where the EI issuing server 1 exchanges trust information 954 the EI trusted module 922, and where the set up processing 936 exchanges set up verification 956 with the EI trusted module 922 to verify the new EI. The agreement information 1150 includes one or more of brand identifiers of a cross-brand utilization agreement rule, utilization restrictions, a rule identifier, and an exchange item identifier.

Having generated the new exchange item, the set up processing 936 receives brand swap information 1250 from the EI buyer computing device 926, where the brand swap information 1250 includes a request to swap a first brand of the EI to a second brand in accordance with the swap rule. For example, the EI buyer computing device 926 determines to swap brands, generates the brand swap information 1250, and sends the brand swap information 1250 to the marketplace server 18. The brand swap information includes one or more of an exchange item identifier, a brand 1 identifier, a brand 2 identifier, a EI buyer computing device identifier, an EI rule, a signature over the brand swap information, and a request to swap the brands.

With the marketplace server 18 receiving the brand swap information 1250, the rule processing 942 validates the brand swap information 1250 in accordance with a secure custody protocol. For example, the rule processing 942 obtains a portion of a blockchain ledger associated with the exchange item and the swap rule, validates the portion of the blockchain ledger, and when the portion is valid, indicate status of the validating (i.e., indicate valid when the rule enables changing from the brand 1 to the brand 2).

When valid, the set up processing 936 facilitate swapping of the brand associated with the exchange item from the brand 1 to the brand 2. The facilitating includes one or more of the set up processing 936 taking control of the exchange item utilizing the secure custody protocol, modifying the portion of the blockchain ledger to indicate that the brand is associated with the brand 2 and is disassociated with a brand 1, determining payment information (in accordance with a payment rule of the exchange item), and facilitating payment (i.e. such as the EI issuing server 2 issuing payment information 1252 to the marketplace server 18, where the marketplace server 18 distributes payment information to the EI issuing server 1). The payment information 1252 includes one or more of the exchange item identifier, the brand 1 identifier, the brand 2 identifier, the agreement information 1150, and payment information to the brand 1 (e.g., to buy out the exchange item).

FIG. 12B is a logic diagram of an embodiment of a method for modifying brand affiliation of an exchange item in an exchange item marketplace network. The method includes step 1260 where a processing module (e.g., of a marketplace server) generates an exchange item (EI) associated with a first brand, where a brand swap rule is associated with the EI. The generating includes one or more of communicating EI information with a first brand server, where the EI information includes a brand swap rule, and where the first brand server exchanges agreement information with a second brand server to establish the brand swap rule.

The method continues at step 1262 where the processing module receives a brand swap request for the EI from a computing device, where the brand swap request identifies a second brand. For example, a computing device in control of the EI (i.e., in accordance with a secure custody protocol) determines to swap brands the first brand to the second brand, generates the brand swap request includes an identifier of the EI, a brand change request, and an identifier of the second brand, and sends the brand swap request to the processing module.

The method continues at step 1264 where the processing module validates the brand swap request in accordance with a secure custody protocol. For example, the processing module obtains a portion of a blockchain ledger associated with the exchange item and the swap rule, validates the portion of the blockchain ledger, and indicate status of the validating (i.e., to change from brand 1 to brand 2).

When valid, the method continues at step 1266 where the processing module facilitates updating of the exchange item to associate the exchange item with the second brand. For example, the processing module takes control of the exchange item utilizing the secure custody protocol, modifies the portion of the blockchain ledger to indicate that the brand is associated with the brand 2 and is disassociated with the brand 1, determines payment information (i.e. in accordance with a payment rule of the exchange item), and facilitates payment, where the processing module distributes payment information (e.g., from the second brand to the first brand).

FIG. 13A is a schematic block diagram of another embodiment of an exchange item marketplace network that includes the EI issuing server 920 of FIG. 6, the EI trusted module 922 of FIG. 6, the marketplace server 18 of FIG. 6, the marketplace database 20 of FIG. 6, the EI buyer computing device 926 of FIG. 6, the point-of-sale (POS) equipment 32 of FIG. 1, and the merchant server 924 of FIG. 6. Each EI buyer computing device may be implemented utilizing the EI buyer computing device 926 of FIG. 6. The EI buyer computing device 926 includes the digital wallet 944 of FIG. 6. The marketplace server 18 includes the set up processing 936 of FIG. 6, the use processing 940 of FIG. 6, and the rule processing 942 of FIG. 6. The exchange item marketplace network functions to offer an exchange item in response to a use pattern.

In an example of operation of the offering of the exchange item in response to the use pattern, the rule processing 936 interprets a redemption monitoring rule associated with one or more exchange items as redeemed by the EI buyer computing device 926. The interpreting includes one or more of obtaining a record associated with the one or more exchange items, extracting a rule portion, and interpreting the rule portion (e.g., what type of use pattern to record, how long, which exchange items, amount of purchases, dates of purchases, timing between purchases, etc.).

When the interpretation indicates to report EI use information 1270 to the EI issuing server 920, the use processing 940 issues the EI use information 1270 to the EI issuing server 920, where the EI use information 1270 corresponds to redemption of the one or more exchange items in accordance with the interpreted redemption monitoring rule. The issuing includes one or more of the rule processing 942 interpreting a rule, the use processing 940 monitoring the redemption of one or more exchange items in accordance with the redemption monitoring rule (e.g., extracting pertinent use information from received merchant use information 980 from the merchant server 924, where the merchant server 924 receives buyer use information from the EI buyer computing device 926 via the point-of-sale equipment 32), generating the EI use information 1270, and sending the EI use information 1270 to the EI issuing server 920.

When receiving further EI use information 1270 from the EI issuing server 920 in response to the EI use information 1270, the set up processing 936 exchanges set up information 958 with the EI buyer computing device 926 to facilitate a potential modification for purchase of another exchange item. The exchanging includes one or more of receiving EI info 950 and/or EI rule set 952 from the EI issuing server 920, where the EI issuing server 920 exchanges trust information 954 with the EI trusted module 922, and where the EI trusted module 922 exchanges set up verification 956 with the set up processing 936 to generate a modified and/or new exchange item; sending the set up information 958 to the EI buyer computing device 926 (e.g., making an offer), where the set up information includes the modified and/or new exchange item, and receiving set up information 958 from the EI buyer computing device 926 with regards to obtaining the modified and/or new exchange item (e.g., accepting or rejecting the offer).

Having exchanged the set up information 958, the set up processing 936 facilitates completion of the modification or purchase of the other exchange item in accordance with the set up information 958 from the EI buyer computing device 926. The facilitating includes one or more of interpreting a response from the EI buyer computing device to indicate a purchase, associating the modified and/or new exchange item with the EI buyer computing device 926 (i.e., facilitating transfer of control to the EI buyer computing device in accordance with a secure custody protocol), and updating the marketplace database 20.

FIG. 13B is a logic diagram of an embodiment of a method for offering an exchange item in response to a use pattern in an exchange item marketplace network. The method includes step 1280 where a processing module (e.g., of a marketplace server) interprets a redemption monitoring rule associated with one or more exchange items associated with the computing device. Interpreting includes one or more of obtaining a record associated with the one or more exchange items, extracting a rule portion, and interpreting the rule portion.

When the interpretation indicates to report EI use information to an associated brand server, the method continues at step 1282 where the processing module issues the EI use information to the brand server. The issuing includes one or more of monitoring redemption of the one or more exchange items to generate the EI use information and sending the EI use information to the brand server in accordance with the redemption monitoring rule (e.g., to a particular brand server in accordance with the redemption monitoring rule).

When receiving further EI information from the brand server in response to the EI use information, the method continues at step 1284 where the processing module exchanges set up information with the computing device to facilitate a potential EI modification or purchase of another EI. The exchanging includes one or more of receiving the EI information and/or EI rule set from the brand server with regards to a modified and/or new exchange item, issuing the set up information to the computing device, where the set up information includes the modified and/or new exchange item, and receiving set up information from the computing device with regards to obtaining the modified and/or new EI.

The method continues at step 1286 where the processing module facilitates completion of a transaction to provide a modified EI or another EI. The facilitating includes one or more of interpreting a response from the computing device to indicate purchase, associating the modified and/or new EI with the computing device (i.e., facilitate transfer of control to the computing device in accordance with a secure custody protocol), and updating a marketplace database to indicate completion of the transaction.

FIGS. 14A and 14B are schematic block diagrams of another embodiment of an exchange item marketplace network that includes the exchange item (EI) issuing server 920 of FIG. six, the EI trusted module 922 of FIG. 6, the EI buyer computing device 926 of FIG. 6, the point-of-sale (POS) equipment 32 of FIG. 1, the merchant server 924 of FIG. 6, the marketplace server 18 of FIG. 6, and the marketplace database 20 of FIG. 6. The EI buyer computing device 920 includes the digital wallet 944 of FIG. 6. The marketplace server 18 includes the set up processing 936 of FIG. 6 and the use processing 940 of FIG. 6. The exchange item marketplace network functions to authorize exchange item redemption.

FIG. 14A illustrates an example of the authorizing of the exchange item redemption where the set up processing 936 receives EI information 950 from the EI issuing server 920 to establish an exchange item within the marketplace. The receiving may be in response to a new exchange item establishment request and/or in response to an initial owner computing device facilitating sale of the exchange item via the marketplace. The receiving may further include the EI issuing server 920 and the EI trusted module 922 exchanging trust information 954 and the EI trusted module 922 exchanging set up verification 956 with the set up processing 936 to complete verification of the exchange item.

The EI information 950 includes an exchange item serial number as originally issued by at least one of the brand server 26 of FIG. 1, the processor server 28 of FIG. 1, and the distributor server 30 of FIG. 1. The exchange item serial number includes a static portion and a dynamic portion, where all bits of the serial number are static portion bits when there are no dynamic portion bits when each bit of the serial number may be either a static portion bits or a dynamic portion bit. A static portion bit is intended not to change over time frame of utilization of the exchange item where a dynamic portion bit may change from time to time.

Having received the EI information, the set up processing 936 generates EI security parameters 1290 for the exchange item. The generating may be based on one or more of a predetermination, system registry information, a security requirement, and a request. The EI security parameter 1290 includes one or more of a secret key, a time interval, a generator algorithm identifier (ID), and a combiner algorithm ID. The generating of the EI security parameters 1290 includes one or more of generating the secret key (e.g., anonymously in a random fashion, subsequently in conjunction with the EI buyer computing device 926 utilizing a Diffie Hellman approach), selecting the time interval, selecting the generator algorithm ID, and selecting the combiner algorithm ID.

Having generated the EI security parameters 1290, the set up processing 936 stores the EI information 950 and the EI security parameters 1290 and the marketplace database 20. Having performed the storing, when the EI is purchased by the EI buyer computing device 926, the set up processing 936 sends the EI information 950 and the EI security parameters 1290 to the EI buyer computing device 926 for storage in the digital wallet 944 for a subsequent EI redemption operation. For example, the set up processing 936 identifies the EI purchase (e.g., a request from the EI buyer computing device 926 that identifies the EI serial number), accesses the marketplace database 20 based on the EI serial number, retrieves the associated EI information 950 and the EI security parameters 1290, and transmits the EI information 950 and the EI security parameters 1292 the EI buyer computing device 926. Alternatively, the EI security parameter 1292 include parameters to establish the secret key between the set up processing 936 and the EI buyer computing device 926 utilizing the Diffie Hellman approach such that the secure key is not passed the marketplace server 18 and the EI buyer computing device 926.

FIG. 14B further illustrates the example of the authorizing of the exchange item redemption where, when the EI buyer computing device 926 redeems the EI, the use processing 940 receives merchant use information 980 (i.e., redemption transaction information, a merchant ID, a brand ID) and dynamic EI information 1292 (e.g., a secure version of the EI info received from the merchant server 924 via the POS equipment 32), where the EI buyer computing device 926 generates the dynamic EI information 1292 based on the EI information 950 utilizing the EI security parameters 1290, where the EI buyer computing device generates buyer use information 976 (e.g., redemption transaction information: purchase amount, identifier of an item purchased, etc.), and where the merchant server 924 issues the merchant use information 980 to the use processing 940 based on the buyer use information 976 received from the EI buyer computing device 926 via the POS equipment 32 (e.g., received via one or more of magnetic stripe, security chip, QR code, barcode, 3-D barcode, manual entry, etc.). The generating of the dynamic EI information 1292 is discussed in greater detail with reference to FIG. 14C.

Having received the dynamic EI information 1292, the use processing 940 verifies the dynamic EI information 1292 to produce authorization information (e.g., authorized or not authorized to redeem the EI). The verifying includes comparing the received dynamic EI information 1292 to locally generated dynamic EI information 1292, indicating a favorable authorization when the comparison is favorable (i.e., a dynamic EI serial number matches), where the use processing 940 retrieves the EI information 950 and the EI security parameters 1292 from the marketplace database 20 and generates the locally generated dynamic EI information based on the retrieved EI information 950 and the EI security parameter 1290. The generating of the locally generated dynamic EI information is discussed in greater detail with reference to FIG. 14C.

These processing 940 may further verify the redemption of the EI. For example, the use processing 940 retrieves the EI serial number from the EI information 950 (i.e., from the marketplace database 20), issues a supplemental use verification request 1294 (i.e., EI info, redemption transaction info) to the EI issuing server 920 that includes the EI information 950 and the information of the redemption (e.g., merchant use information 980), and interpret a received supplemental use verification response 1296 (i.e., EI info, redemption transaction info, approval status: yes/no) to produce a further indication of authorization (i.e., indicate favorable authorization when the response is favorable, such as when the EI trusted module 922 and/or the EI issuing server 920 verify that a remaining balance of the exchange item (e.g., based on the static portion of the EI serial number) is sufficient to provide payment for a purchase associated with the redemption of the exchange item).

FIG. 14C is a schematic block diagram of an embodiment of the use processing of FIGS. 14A-B that includes a dynamic number generator 1298 and a combiner 1300 to generate the locally generated dynamic EI information. Alternatively, or in addition to, the use processing 940 may be implemented with a processing module of the EI buyer computing device 926 to generate the dynamic EI information 1292. The use processing receives the EI information 950, a time 1302 (e.g., real-time), and the EI security parameters 1292 produce the dynamic EI information. The dynamic number generator 1298 and the combiner 1300 may be implemented utilizing one or more of the processing module 62 of FIG. 2, the computing core 52 of FIG. 2, and the computing core 122 of FIG. 3.

In an example of operation of the generating of the dynamic EI information, the dynamic number generator 1298 applies one or more deterministic functions (e.g., a hash based message authentication code (HMAC), a sponge function, a hashing function, a signature function, a cyclic redundancy check (CRC), a checksum function, and a mask generating function (MGF) in accordance with the generator algorithm ID 1308 (e.g., to select which deterministic function(s)) to the time 1302 (e.g., real-time) in accordance with a time interval increment 1306 utilizing a secret key 1304 to produce a dynamic EI number portion 1314. For example, the dynamic number generator 1298 selects the HMAC based on the generator algorithm ID 1308, represents the time 1302 within a 30 second interval (i.e., xx:xx:00 or xx:xx:30) when the time interval increment 1306 indicates 30 second intervals, and applies the HMAC function to the represented time utilizing the secret key 1304 to produce an HMAC function output as the dynamic EI number portion 1314.

With the dynamic EI number portion 1314 produced, the combiner combines the dynamic EI and a static EI number portion 1312 of the EI information 950 in accordance with a combiner algorithm ID 1310 of the EI security parameters 1292 produce the dynamic EI information. The dynamic EI information produces a secure version of the EI serial number, where a portion of the secure version includes static bits of the static EI number portion 1312 and dynamic bits of the dynamic EI number portion 1314 in accordance with the combiner algorithm ID 1310. The combiner algorithm ID indicates which bits are to be utilized for static bits and which bits are to be utilized for dynamic bits. Alternatively, or in addition to, the combiner 1300 may utilize one or more other variables to produce the static and dynamic bits, where the one or more other variables includes one or more of the time 1302, the secret key 1304, the time interval increment 1306, and the generator algorithm ID 1308. The combiner 1300 may replace static bits of the EI serial number with dynamic bits including replacement of most significant bits, middle bits, we significant bits, random bits, a combination, a personal identification (PIN) portion, etc. For example, the combiner 1300 utilizes most significant bits associated with 10 most significant numbers of the EI serial number and we significant bits of the dynamic EI number portion 1314 to generate 6 least significant numbers of the EI serial number to produce a 16-digit secure version of the EI serial number.

FIG. 14D is a logic diagram of an embodiment of a method for authorizing exchange item redemption in an exchange item marketplace network. The method includes step 1320 where a processing module (e.g., of a marketplace server) receives exchange item (EI) info to establish and EI within the exchange item marketplace network. The receiving includes receiving the EI info in response to a new EI establishment request and receiving the EI info in response to an initial owner computing device facilitating sale of the EI.

The method continues at step 1322 where the processing module generates EI security parameters for the EI. The generating may be based on one or more of a predetermination, system registry information, a security requirement, and a request. For example, the processing module randomly generates a secret key to associate with the EI, selects a time interval increment for subsequent processing of a real-time value within an interval of the time increment, selects a generator algorithm ID (e.g., selection of one or more deterministic functions), and selects a combiner algorithm ID (e.g., for subsequent combining of static and dynamic portions of an EI serial number to generate a secure version of an EI serial number of the EI).

The method continues at step 1324 where the processing module stores the EI info and the EI security parameters in a marketplace database. For example, the processing module facilitates storage of the EI info and the EI security parameters based on the EI serial number in the marketplace database.

When the EI is to be associated with a computing device, the method continues at step 1326 where the processing module sends the EI info in the EI security parameters to the computing device. For example, the processing module identifies the EI purchase, accesses the marketplace database based on the serial number of the EI, retrieves the EI information and the associated EI security parameters, and transmits the EI information and the EI security parameters to the computing device. As another example, the processing module identifies the EI purchase, accesses the marketplace database based on a serial number of the EI, retrieves the EI information and the associated EI security parameters, performs a Diffie Hellman approach with the computing device to produce the secret key, and transmits the EI information, the associated EI security parameters, and the produced secret key to the computing device.

When the computing device redeems the EI, the method continues at step 1328 where the processing module receives merchant use information and dynamic EI information generated by the computing device, where the computing device generates the dynamic EI information based on the EI info utilizing the EI security parameters (e.g., performs a HMAC on a time interval adjusted representation of real-time utilizing the secret key). The method continues at step 1330 where the processing module verifies the received dynamic EI information to produce authorization information. The verifying includes comparing the received dynamic EI information to locally generated dynamic EI information and indicating favorable authorization when the comparison is favorable (i.e., secure versions of the EI serial number match), where the processing module retrieves the EI information and the EI security parameters from the marketplace database, generates the locally generated dynamic EI information based on the retrieved EI information and EI security parameters. The processing module may make a minor adjustment to the time interval representation of real-time when the comparison is unfavorable in an attempt to match the secure versions of the EI serial number (e.g., plus or minus 1 or 2 time intervals).

When the authorization information is favorable, the method continues at step 1332 where the processing module further verifies the EI redemption to produce further authorization information. For example, the processing module retrieves the EI serial number from the EI information of the marketplace database, issues a supplemental use verification request to an EI issuing server, where the supplemental use verification request includes the EI information and information of the redemption, and interprets a received supplemental use verification response to produce a further indication of authorization (e.g., indicates favorable authorization when the response is favorable, such as when a remaining balance of the EI is sufficient to provide payment for a purchase of the redemption).

FIG. 15A is a schematic block diagram of another embodiment of an exchange item marketplace network that includes the initial owner computing device 928 of FIG. 6, the exchange item (EI) issuing server 920 of FIG. 6, the EI trusted module 922 of FIG. 6, the marketplace server 18 of FIG. 6, and the marketplace database 20 of FIG. 6. The initial owner computing device 928 includes the digital wallet 946 of FIG. 6. The marketplace server 18 includes the set up processing 936 of FIG. 6, the use processing 940 of FIG. 6, and the rule processing 942 of FIG. 6. The exchange item marketplace network functions to replace a fraudulently obtained exchange item.

In an example of operation of the replacing of the fraudulently obtained exchange item, set up processing 936 enters a new exchange item in the marketplace database 20. The entering includes interpreting received sale information 966 from the initial owner computing device 928, exchanging EI information 950 and an EI rule set 952 with the EI issuing server 920, and initiating validation of the new exchange item, where at least one EI rule of the EI rule set 952 indicates replacement of a fraudulent EI, where the EI issuing server 920 exchanges trust information 954 with the EI trusted module 922, and where the EI trusted module 922 exchanges set up verification 956 with the set up processing 936 to conclude validation of the new EI (i.e., valid meaning balance, valid EI serial number, etc.), generating a record for the new EI, and storing the record for the new EI in the marketplace database 20 in accordance with a secure custody protocol (e.g., updating a blockchain ledger).

Having entered the new exchange item into the marketplace database 20, the use processing 940 detects a fraudulent EI. The detecting includes one or more of interpreting fraud information 1336 received from the EI issuing server 920 (i.e., the initial owner computing device utilized a stolen credit card to purchase the EI from the EI issuing server), interpreting a fraud analysis of the EI record from the marketplace database, and issuing fraud information 1336 to the EI issuing server 920.

When an EI rule associated with the EI record indicates replacement of a fraudulent EI, the marketplace server 18 generates a replacement EI record based on the fraudulent EI. For example, the rule processing 942 interprets the EI rule to indicate the replacement of the fraudulent EI, the set up processing 936 extracts EI parameters from the fraudulent EI, generates the replacement EI record utilizing the extracted EI parameters in accordance with the EI rule indicating replacement of the fraudulent EI (i.e., adjust balance, adjust other associated rules, etc.). Having generated the replacement EI record, the set up processing 936 updates the marketplace database 20 to include the replacement EI and to exclude the fraudulent EI.

FIG. 15B is a logic diagram of an embodiment of a method for replacing a fraudulently obtained exchange item in an exchange item marketplace network. The method includes step 1340 where a processing module (e.g., of a marketplace server) enters and exchange item (EI) into a marketplace database, where a fraud status of the EI is unknown. The entering includes one or more of interpreting received sale information from a selling computer device, exchanging EI information and an EI rule set with an EI issuing server to initiate validation of the new exchange item, generating a record for the EI, and storing the generated record for the EI in the marketplace database in accordance with a secure custody protocol (i.e., updated blockchain ledger).

The method continues at step 1342 where the processing module determines the fraud status of the EI as fraudulent to produce a fraudulent EI. The determining includes one or more of interpreting fraud information received from the EI issuing server (i.e., the selling computer device utilized a stolen credit card to purchase the EI from the EI issuing server), interpreting a fraud analysis of the EI record from the marketplace database (e.g., previous fraud history), and issuing fraud information to the EI issuing server (e.g., sending the previous fraud history to enable the EI issuing server to interpret the previous fraud history to produce a updated fraud status).

When an EI rule associated with the fraudulent EI indicates replacement of the fraudulent EI, the method continues at step 1344 where the processing module generates a replacement EI based on the fraudulent EI. The generating includes one or more of extracting EI parameters from the fraudulent EI, and generating the replacement EI utilizing the extracted EI parameters in accordance with the EI rule indicating replacement of the fraudulent EI) e.g., adjusting a remaining balance, adjusting other associated EI rules, etc.). Having generated the replacement EI, the method continues at step 1346 where the processing module updates the marketplace database to exclude the fraudulent EI and to include the replacement EI.

FIG. 16A is a schematic block diagram of another embodiment of an exchange item marketplace network that includes exchange item (EI) buyer computing device 926 of FIG. 6, the marketplace server 18 of FIG. 6, and the marketplace database 20 of FIG. 6. The EI buyer computing device 926 includes the digital wallet 944 of FIG. 6. The marketplace server 18 includes the set up processing 936 of FIG. 6, the use processing 940 of FIG. 6, and the rule processing 942 of FIG. 6. The exchange item marketplace network functions to establish a fraud status for an account of the exchange item marketplace network.

In an example of operation of the establishing of the fraud status, the set up processing 936 processes an acquisition transaction by the EI buyer computing device 926 to acquire an exchange item represented in the marketplace database 20. The processing includes exchanging set up information 958 between the set up processing 936 and the EI buyer computing device 926, where the set up information 958 includes one or more of an EI serial number, a brand identifier (ID), a user account number, a credit card number, a timestamp, and an unknown fraud status level.

Having processed the acquisition transaction, the set up processing 936 establishes a record of the transaction in the marketplace database in accordance with a secure custody protocol. For example, when a fraud risk evaluation outcome is favorable, the set up processing 936 updates a blockchain ledger associated with the exchange item to include account information 1350 (i.e., take control of the blockchain ledger utilizing a private key associated with the marketplace server), where the account information 1350 includes at least a portion of the set up information 958.

Having established the record of the transaction, when determining that the acquisition transaction as fraudulent, and when the rule processing 942 indicates to update the record, one or more of the set up processing 936 and the use processing 940 updates the record of the transaction in the marketplace database to associate the fraudulent transaction with the account number corresponding to the EI buyer computing device. The updating includes modifying a portion of the blockchain ledger associated with the account number to indicate that the buyer computing device 926 is associated with fraud for subsequent utilization in fraud risk evaluations.

FIG. 16B is a logic diagram of an embodiment of a method for establishing a fraud status for an account in an exchange item marketplace network. The method includes step 1360 where a processing module (e.g., of a marketplace server) processes an exchange item (EI) acquisition transaction from a buyer computing device to acquire an EI represented in a marketplace database. The processing includes exchanging set up information with the buyer computing device (e.g., EI serial number, a brand identifier, a user account number, a credit card number, another EI serial number utilized for purchase of the EI, a timestamp, and an unknown fraud status).

When a fraud risk evaluation outcome is favorable, the method continues at step 1362 where the processing module establishes a record of the transaction in the marketplace database in accordance with a secure custody protocol that associates the buyer computing device to the transaction. For example, when a fraud risk evaluation outcome is favorable (e.g., performing a lookup in the marketplace database of the account information associated with the buyer user device), the processing module updates a blockchain ledger associated with the exchange item to include account information (i.e., take control of the blockchain ledger utilizing a private key associated with the marketplace server), where the account information includes at least a portion of the set up information.

When determining that the acquisition transaction is fraudulent, the method continues at step 1364 where the processing module updates the record of the transaction in the marketplace database to associate the fraudulent transaction with the buyer computing device for utilization in a subsequent fraud risk evaluation. For example, the processing module modifies a portion of the blockchain ledger associated with the account number to indicate that the buyer computing devices associated with fraud for utilization in subsequent fraud risk evaluations.

FIG. 17A is a schematic block diagram of another embodiment of an exchange item marketplace network that includes exchange item (EI) buyer computing device 926 of FIG. 6, the merchant server 924 of FIG. 6, the marketplace server 18 of FIG. 6, and the marketplace database 20 of FIG. 6. The EI buyer computing device 926 includes the digital wallet 944 of FIG. 6. The marketplace server 18 includes the use processing 940 of FIG. 6 and the rule processing 942 of FIG. 6. The exchange item marketplace network functions to facilitate restitution for unfavorable exchange item redemption.

In an example of operation of the facilitating of the restitution, the use processing 940 receives merchant use information 980 from the merchant server 924 indicating an EI redemption request from the EI buyer computing device 926 with regards to a particular item, where the particular item is to be delivered by a merchant associated with the merchant server 924 to a user of the EI buyer computing device 926. For example, the EI buyer computing device selects the exchange item from the digital wallet 944 associated with particular item, the EI buyer computing device 926 issues buyer use information 976 to the merchant server 924, and the merchant server 924 issues the merchant use information 980 to the use processing 940.

Having received the merchant use information 980, the use processing 940 processes the EI redemption request. For example, the use processing 940 validates the EI, confirming that a remaining balance associated with the EI is sufficient for redemption with regards to the particular item, and updates a portion of a blockchain ledger stored in the marketplace database 20 to indicate an updated remaining balance of the EI and at least some of the merchant use information 980.

When the use processing 940 receives unfavorable delivery information 1370 (e.g., indicating a delivery has not yet been completed within an expected delivery time frame) from the EI buyer computing device 926, the rule processing 942, based on an output of the rule processing 942 interpreting an EI rule associated with the EI, selects a restitution approach. The selecting includes interpreting the EI rule associated with the portion of the blockchain ledger of the exchange item within the marketplace database, where the EI rule indicates a particular type of restitution (i.e., refunding a purchase price of the exchange item, reinstating the remaining balance of the EI, providing the buyer computing device with another EI, and initiating and investigation, and providing investigation results to the buyer computing device).

Having selected the restitution approach, these processing 940 executes restitution in accordance with the selected restitution approach. For example, the use processing 940 performs a function specified by the restitution approach when delivery of the particular item has not occurred.

FIG. 17B is a logic diagram of an embodiment of a method for facilitating restitution for unfavorable exchange item redemption. The method includes step 1380 where a processing module (e.g., of a marketplace server) receives an EI redemption request from a buyer computing device with regards to a particular item, where the particular item is to be delivered by a merchant to a user of the buyer computing device. For example, the buyer computing device selects an exchange item from the digital wallet, the buyer computing device issues buyer use information to a merchant server associated with the merchant, and the merchant server issues merchant use information to the processing module that includes at least some of the buyer use information.

The method continues at step 1382 where the processing module facilitates the EI redemption request for the particular item such that the particular item is to be delivered by the merchant to the user. For example, the processing module validates the EI, confirming that a remaining balance associated with the EI is sufficient for redemption with regards to purchase of the particular item, and updates a portion of a blockchain ledger stored in a marketplace database (or received from the buyer computing device) to indicate an updated (i.e., lowered) remaining balance of the EI and at least some of the merchant use information.

When detecting an unfavorable delivery condition, the method continues at step 1384 where the processing module selects a restitution approach. The selecting includes one or more of receiving an indication indicating that delivery has not been completed within an expected delivery time frame, and interpreting an EI rule associated with a portion of the blockchain ledger of the exchange item within the marketplace database, where the EI rule indicates a particular type of restitution.

The method continues at step 1386 where the processing module executes restitution in accordance with the restitution approach. For example, the processing module performs the function specified by the restitution approach, verifies restitution, and when verified, updates the blockchain ledger to indicate that the restitution has been executed and/or favorably completed.

FIG. 18A is a schematic block diagram of another embodiment of an exchange item marketplace network that includes the initial owner computing device 928 of FIG. 6, the marketplace server 18 of FIG. 6, the marketplace database 20 of FIG. 6, and one or more EI buyer computing devices 926 of FIG. 6. The initial owner computing device 928 includes the digital wallet 946 of FIG. 6. The marketplace server 18 includes the set up processing 936 of FIG. 6 and the rule processing 942 of FIG. 6. Each EI buyer computing device 926 includes the digital wallet 944 of FIG. 6. The exchange item marketplace network functions to redistribute an exchange item.

In an example of operation of the redistributing of the exchange item, when receiving an updated EI rule set 1390 from the initial owner computing device, the set up processing 936 modifies one or more EI rules corresponding to an exchange item associated with the initial owner computing device 928. The modifying includes one or more of the rule processing 942 verifying an existing EI rule includes permissions to allow the initial owner computing device 928 to facilitate modification of the one or more EI rules (i.e., interpret the existing EI rule), modifying one or more EI rules in accordance with the updated EI rule set, where the modified one or more EI rules indicates redistribution instructions with regards to enabling utilization of the EI by one or more other EI buyer computing devices. The redistribution instructions include one or more of a use restriction, a timing restriction, restriction, a regifting restriction, and a utilization level of a maximum portion of a remaining balance of the EI, etc.

Having modified the one or more EI rules, the setup processing 936 facilitate storage of the modified one or more EI rules associated with the EI in the marketplace database 20 in accordance with a secure custody protocol. For example, the setup processing 936 generates updated EI information and stores the updated EI information and the updated EI rules 1392 in the marketplace database 20 in accordance with the secure custody protocol (i.e., updating a portion of a blockchain ledger utilizing a private key associated with the marketplace server 18).

Having facilitated the storage of the modified one or more EI rules, the setup processing 936 issues redistribution set up information 1394 to the one or more EI buyer computing devices 926 such that the one or more EI buyer computing devices 926 may subsequently redeem at least a portion of the EI in accordance with the modified one or more EI rules. For example, the setup processing 936 generates the redistribution set up information 1394 to include at least a portion of the updated EI rules and updated EI information (i.e., the blockchain ledger), and sends the redistribution set up information 1394 to the one or more EI buyer computing devices 926 for storage in corresponding digital wallets 944.

FIG. 18B is a logic diagram of an embodiment of a method for redistributing an exchange item in an exchange item marketplace network. The method includes step 1400 where a processing module (e.g., of a marketplace server) modifies one or more exchange item (EI) rules corresponding to an exchange item associated with an owner computing device in accordance with a received updated EI rule set. For example, the processing module verifies an existing EI rule permissions to allow the owner computing device to facilitate modification of the one or more EI rules (i.e., interpret the existing EI rule), and modifies the one or more EI rules in accordance with the updated EI rule set, where the modified one or more EI rules indicates redistribution instructions with regards to enabling utilization of the EI by one or more other computing devices.

The method continues at step 1402 where the processing module stores the modified one or more EI rules in a marketplace database in accordance with a secure custody protocol. For example, the processing module generates updated EI information and stores the updated EI information and the updated EI rules in the marketplace database in accordance with the secure custody protocol (i.e., updating a portion of a blockchain ledger).

The method continues at step 1404 where the processing module issues redistribution set up information to one or more other computing devices such that the one or more other computing devices may subsequently redeem at least a portion of the EI in accordance with the modified one or more EI rules and the secure custody protocol. For example, the processing module generates the redistribution set up information to include at least a portion of the updated EI rules and updated EI information (i.e., the blockchain ledger), selects the one or more other computing devices in accordance with the redistribution instructions, and sends the redistribution set up information to the one or more other computing devices for storage in corresponding digital wallets.

FIG. 19 is a schematic block diagram of another embodiment of an exchange item marketplace network that includes a server 18, a plurality of computing devices (e.g., user devices 12-16), and the database(s) 20. Associated with each computing device #1-#n is a digital wallet 35, 27, and 41. Each digital wallet stores a replicated copy of an exchange item 33, 39, and 43 as will subsequently discussed.

The database 20 stores issuer agreements 27 and exchange item rules 29. An issuer agreement is an agreement between an issuer of exchange items (e.g., a hardware chain issuing gift cards) and an operator of the network regarding a variety of aspects the exchange items. For example, the issuer agreement includes information regarding one or more of: re-selling of exchange items, use restrictions of exchange items, promotional options, use permissions of exchange items, sharing options of exchange items, cross-branding options (e.g., allowing hardware chain gift cards to be used at retailers other than hardware chain franchises), expiration information, transferring information, etc. Typically, the issuer agreement covers a majority, if not all, of the issuer's exchange items that are available and/or usable in the computing network.

For specific types of exchange items (down to an individual exchange item), exchange item rules are created. The rules include one or more of: condition based rules (e.g., 10% off purchase price within 12 hours after a home team victory), transfer restrictions, use restrictions, use permissions, sharing options, etc. When an exchange item is covered by both an issuer agreement and exchange item rules, the rules or the agreement take priority; typically, the rules will have priority over the issuer agreement. For example, the issuer agreement indicates sharing an exchange item by authorized groups is allowable, however, the rules for a specific exchange item of the issuer indicates that sharing is not allowed. In this example, the rules take precedence and sharing is not allowed for this particular exchange item.

As an example of sharing an exchange item, a first computing device obtains 23 a digital exchange item 21 (e.g., a computer generated and readable version of a gift card). For example, the first computing device purchases the digital exchange item 21 via a resale process of the network, directly from a bulk distributor, or from an issuing brand of the exchange item (e.g., the hardware chain that issued the gift card). As another example, the first computing device receives the exchange item as a gift.

The first computing device then sends a share request 25 to the server 18 to share the exchange item (e.g., gift card) with a group of computing devices #1-#n (e.g., computing devices of family members of a person affiliated with the first computing device). The server determines whether this particular exchange item can be shared by accessing applicable issuer agreement(s) and applicable exchange item rules. For example, the server accesses the issuer agreement and the rules to determine whether this particular exchange item can be shared. If it can be shared, are there any restrictions, any computing devices excluded from sharing, does the first computing device have authorization to share the exchange item, etc.

When the exchange item can be shared, the server 18 establishes secure custody rights for each computing device in the group and determines sharing rights regarding the digital exchange item. The server establishes secure custody rights by recording sharing of the exchange item among the computing devices in the group in a digital chain of custody of the exchange item. The digital chain of custody will be described in greater detail with reference to one or more of the subsequent figures.

The server determines the sharing rights of the exchange rights in a variety of ways. For example, the first computing device provides the sharing rights to the server, where the sharing rights indicates group level permissions, group level restrictions, group level conditions, individual permissions, individual conditions, and/or individual restrictions. As another example, the server accesses a look up table that specifies the sharing rights based on a group identifier, the type of exchange item, etc. Further examples of the sharing rights will be discussed with reference to one or more of the subsequent figures.

When the secure custody and sharing rights have been created, the server creates replications of the digital exchange item. The server then upload the replications of the digital exchange item to digital wallets associated with the computing devices in the group. In particular, the digital wallet 35 of computing device #1 receives a replication of the digital exchange item; the digital wallet 37 of computing device #2 receives a replication of the digital exchange item; and so on. The replication of the digital exchange item is a computer generated and computer readable file that represents the exchange item (e.g., a gift card, a voucher, a store credit, etc.).

The server also uploads the sharing rights of the exchange item to the digital wallets. The sharing rights may be the same for all of the computing devices in the group, may be different for each computing device in the group, or two or more computing devices have common sharing rights, while other computing devices have different sharing rights. Once the digital wallets are updated, any computing device in the group may use the exchange item.

FIG. 20 is a logic diagram of a method of computing devices sharing an exchange item that begins at step at step 51 where the first computing device obtains a digital exchange item that is regarding at least one closed loop financial instrument (e.g., a gift card, a voucher, a store credit, etc.). For example, the first computing device obtains the digital exchange item by purchasing it from a reselling computing device via the computing network, by purchasing it from an issuing server via the computing network, or by receiving it as a gift.

The method continues at step 53 where the first computing device sends, to a server of the computing network, a request to share the digital exchange item with a group of computing devices, which includes the first computing device. The request includes information regarding the exchange item, the group, the first computing device, and/or a request to establish the group. An example of establishing the group will be discussed with reference to FIG. 21.

The method continues at step 55 where the server determines whether the digital exchange item can be shared with the group based on an issuer agreement and/or exchange item rules. Examples of the issuer agreement and exchange item rules were discussed with reference to FIG. 20. When the exchange item cannot be shared, the method continues at step 57 where the server denies the request to share the exchange item.

When the digital exchange item can be shared, the method continues at step 59 where the server establishing secure custody rights for each computing device in the group of computing devices. The server establishes secure custody rights by recording sharing of the exchange item among the computing devices in the group in a digital chain of custody of the exchange item. The digital chain of custody will be described in greater detail with reference to one or more of the subsequent figures.

The method continues at step 61 where the server determines sharing rights regarding the digital exchange item. For example, and with reference to FIG. 24, the server determines that computing device #1 is affiliated with Dad (i.e., the computing device #1 is registered with the network and the user of computing device #1 is recorded to be Dad). The server further determines that computing device #2 is affiliated with Mom, computing device #3 is affiliated with Child #1, and computing device #4 is affiliated with Child #2.

The exchange item that is being shared is a coffee shop gift card with a serial number (sn) of 0010. The server then determines permissions, conditions, and/or restrictions for each user of the group. As an example, the permissions include how the exchange item can be used (e.g., all types of purchases, food purchases only, beverage purchases only, all beverages but coffee, etc.). As another example, the restrictions include limitations on how the exchange item can be used (e.g., a daily spend limit, a location restriction, a time of day restriction, etc.). As yet another example, the conditions include special offers based on the occurrence of a condition. In the example of FIG. 24, Mom and Dad have all permissions and no restrictions, Child #1 and Child #2 have food purchasing permission, Child #1 has a $50 per day limit, and Child #2 has a $35 per day limit and can only purchase food during breakfast and lunch hours.

Returning to the discussion of FIG. 20, the method continues at step 63 where the server generates replications of the digital exchange item (e.g., digital copies of the exchange item that are computer readable). The method continues at step 65 where the server uploads the replications of the digital exchange item and the sharing rights to digital wallets associated with the computing devices of the group such that each computing device has access to the digital exchange item. The method continues at step 67 where the server updates the exchange item database 934 to reflect the sharing of the exchange item.

FIG. 21 is a logic diagram of a further method of step 53 of FIG. 20 regarding computing devices sharing an exchange item. This method begins at step 71 where the first computing devices sends, as part of the request, a request to authenticate the group of computing devices (i.e., set the group up as a valid and trusted group for all types of exchange items, just for this particular exchange item, for a particular type of exchange items (e.g., gift cards from coffee shops), or for exchange items from a particular issuer (e.g., hardware chain store).

The method continues at step 73 where the server authenticates each computing device of the group of computing devices. For example, the server verifies that each computing device is registered with the network, is in good standing with the network, etc. As a further example, the server also verifies that there is some affiliation of the various computing devices with the first computing device (e.g., family members, same billing address, same employer, expressed desired to be affiliated, etc.).

When each computing device has been authenticated, the method continues at step 81 where the server validates, that each computing device desires to be in the group for sharing digital exchange items. For example, the server queries each computing device as to participating in the group. As another example, the server accesses a lookup table to determine group participation of a computing device. When, as determined at step 83, that each computing device desires to be in the group, the method continues at step 87 where the server authenticates the group of computing devices for sharing digital exchange items.

When one or more computing devices have not been authenticated, the method continues at step 77 where the server determines to proceed in authenticating the group with less than all of the computing devices. The server may make such a determination based on feedback from the first computing device, a predetermined protocol, and/or input from other sources in the network. When the server determines not to proceed with less than all of the computing devices, the method continues at step 79, where the server denies the request.

When the server determines to proceed with less than all of the devices, the method continues at step 80, where the server determines which of the available computing devices desires to be in the group. As an alternative to continuing with less than all devices or in denying the request, the server attempts to establish the computing device as authentic by having it register with the system, clearing past infractions that placed the computing device in bad standing with the network, etc.

When less than all of the computing devices desire to be in the group, the method continues at step 85 where the server determines to proceed with less than all of the computing devices. The server may make such a determination based on feedback from the first computing device, a predetermined protocol, and/or input from other sources in the network. When the server determines not to proceed with less than all of the computing devices, the method continues at step 79, where the server denies the request. When the server determines to proceed with less than all, the method continues at step 87 where the server authenticates the group with just the devices that desired to be in the group.

FIG. 22 is a logic diagram of a further method of computing devices sharing an exchange item; in particular step 55 of FIG. 20. This method begins at step 91 where the server determines whether the group of computing devices is an authenticated sharing group. If not, the method continues at step 93 where the server denies the request or attempts to facilitate authentication per FIG. 21.

When the group of computing devices is an authenticated sharing group, the method continues at step 95 where the server determines whether the issuer agreement allows for exchange items to be shared. If not, the method continues at step 97 where the server denies the request or attempts to facilitate a change to the issuer agreement.

When the issuer agreement allows for exchange items to be shared, the method continues at step 99 where the server determines whether the exchange item rules allow for the digital exchange item to be shared. If not, the method continues at step 101 where the server denies the request or attempts to facilitate a rule change. When the exchange item rules allow for the digital exchange item to be shared, the server determine that the digital exchange item can be shared.

FIGS. 23A and 23B are an example of computing devices sharing an exchange item and creating secure data blocks to form a secure chain of custody 115 for the exchange item. For each transaction regarding the exchange item, a secure data block is created. Each secure data block includes a header section and a transaction section. The header section includes information regarding one or more previous transactions (if any), information regarding the current transaction, and may further include a unique transaction identifier (e.g., a unique random number). The transaction section includes information about the transactor, the transactee, and the transaction.

As shown in this example, when the brand server commissions a processor server to create an exchange item, secure data block 0 is created. For this transaction, the brand server is the transactor in the transaction and the processor server is the transactee in the transaction of creating an exchange item. The header section 111 of the secure data block 0 includes information regarding the current transaction of creating the exchange item and may further include a unique transaction identifier. Since this is the first transaction regarding the exchange item, there are no previous transactions, thus the header does not include previous transaction information or may include an indication that this is the first secure data block in the chain of custody 115 for the exchange item. The transaction section 113 includes information regarding the transaction, the transactor, and the transactee. Note that the transaction section 113, or the entire secure data block, may be encrypted with an encryption key (e.g., public key of a private/public key pair) of the transactor and/or of the transactee.

When the processor server creates the exchange item, another secure data block (e.g., block 1) may be created. For this transaction, the processor server is both the transactor and the transactee for the transaction of creating the exchange item and secure data block 1 is created. The header section includes information regarding secure data block 0, information regarding the current transaction, and may further include a unique transaction identifier. The transaction section includes information regarding the processor server as both the transactor and the transactee, and information regarding the current transaction of creating the exchange item. Note that commissioning and creating may be deemed to be one transaction, thus only one secure data block would be created.

At some later point in time, the processor server provides the exchange item to a distributor server for distribution of the exchange item. In this transaction, the processor server is the transactor and the distributor server is the transactee for the transaction of distributing the exchange item for sale. Secure data block 2 is created for this transaction. The header section includes information regarding secure data block 1, information regarding the current transaction, and may further include a unique transaction identifier. The transaction section includes information regarding the processor server as the transactor, the distributor server as the transactee, and information regarding the current transaction of distributing the exchange item for sale.

At a further point in time, the first computing device purchases the exchange item from the distributor server. In this transaction, the distributor server is the transactor and the first computing device is the transactee for the transaction of purchasing the exchange item. Secure data block 3 is created for this transaction. The header section includes information regarding secure data block 2, information regarding the current transaction, and may further include a unique transaction identifier. The transaction section includes information regarding the distributor server as the transactor, the first computing device as the transactee, and information regarding the current transaction of purchasing the exchange item.

Continuing with the example in FIG. 23B, the first computing device sends a share request to the server, which is processed as discussed above. Note that this is not a transaction creating a new secure data block in the secure chain of custody 115. When the sharing request is granted, the server facilitates sharing the exchange item with other computing devices in the group. This may be done individually, creating individual secure data block, or may be done in parallel, creating one secure data block for sharing.

In the present example, a single secure data block is created to establish the sharing. In this transaction, the server is the transactor and the other computing devices are the transactee for the transaction of sharing the exchange item. Secure data block 4 is created for this transaction. The header section includes information regarding secure data block 3, information regarding the current transaction, and may further include a unique transaction identifier. The transaction section includes information regarding the server as the transactor, the other computing devices as the transactee, and information regarding the current transaction of sharing the exchange item with each computing device of the group. The information regarding sharing includes the sharing rights granted to each computing device in the group.

FIG. 25 is an example of a secure data block that includes a header section 111 and a transaction section 113. The header section 111 includes a representation of a previous secure data block (if any), and a representation of the current transactions. Each of the representations may be created by performing a hash function, a deterministic function, and/or an encoding function (e.g., encryption, scrambling, compacting, etc.).

The transaction section 113 includes a digital signature of the transactor, a description of a transaction, and information regarding the transaction. As an example, the description of the transaction is “create exchange item” and the information regarding the transaction is the “exchange item information”, which includes the identity of the exchange item, a brand of the exchange item, time restrictions of the exchange item, a digital image of the exchange item, the authenticated value, and/or use restrictions of the exchange item. The transaction section may further include other transaction descriptions and other transaction information. The transaction section may further include the public key of the transactee and/or may be encrypted using the public key of the transactee.

FIGS. 26A and 26B are another example of creating the header section and the transaction section of a secure data block. In FIG. 26A, the transactee's public key and the transaction section of the previous secure data block are hashed, using a hashing function, to produce a hash result. The hash resultant and the transactor's private key are inputs to a signature function to generate the transactor's signature. Note that the transactee can verify the transactor's signature using the transactor's public key, the transactee's private key, and the representation of the previous secure data block in the header of the current secure data block.

In FIG. 26B, the previous secure data block is an input to hashing function to produce a previous secure data block hash (e.g., a representation of the previous secure data block). A nonce (e.g., a unique arbitrary number) may also be an input to the hashing function to create the previous secure data block hash. In addition, the transaction section of the current secure data block is an input to another hashing function, which produces a current transaction section hash (e.g., a representation of the current transaction). Note that the transaction section includes the transactee's public key, the transactor's signature, transaction description(s), and transaction information. The transaction action section may further include the transactor's public key and may be encrypted using the transactee's public key. The previous secure data block hash and the current transaction section hash form the header section of the current secure data block.

It is noted that terminologies as may be used herein such as bit stream, stream, signal sequence, etc. (or their equivalents) have been used interchangeably to describe digital information whose content corresponds to any of a number of desired types (e.g., data, video, speech, audio, etc. any of which may generally be referred to as ‘data’).

As may be used herein, the terms “substantially” and “approximately” provides an industry-accepted tolerance for its corresponding term and/or relativity between items. Such an industry-accepted tolerance ranges from less than one percent to fifty percent and corresponds to, but is not limited to, component values, integrated circuit process variations, temperature variations, rise and fall times, and/or thermal noise. Such relativity between items ranges from a difference of a few percent to magnitude differences. As may also be used herein, the term(s) “configured to”, “operably coupled to”, “coupled to”, and/or “coupling” includes direct coupling between items and/or indirect coupling between items via an intervening item (e.g., an item includes, but is not limited to, a component, an element, a circuit, and/or a module) where, for an example of indirect coupling, the intervening item does not modify the information of a signal but may adjust its current level, voltage level, and/or power level. As may further be used herein, inferred coupling (i.e., where one element is coupled to another element by inference) includes direct and indirect coupling between two items in the same manner as “coupled to”. As may even further be used herein, the term “configured to”, “operable to”, “coupled to”, or “operably coupled to” indicates that an item includes one or more of power connections, input(s), output(s), etc., to perform, when activated, one or more its corresponding functions and may further include inferred coupling to one or more other items. As may still further be used herein, the term “associated with”, includes direct and/or indirect coupling of separate items and/or one item being embedded within another item.

As may be used herein, the term “compares favorably”, indicates that a comparison between two or more items, signals, etc., provides a desired relationship. For example, when the desired relationship is that signal 1 has a greater magnitude than signal 2, a favorable comparison may be achieved when the magnitude of signal 1 is greater than that of signal 2 or when the magnitude of signal 2 is less than that of signal 1. As may be used herein, the term “compares unfavorably”, indicates that a comparison between two or more items, signals, etc., fails to provide the desired relationship.

As may also be used herein, the terms “processing module”, “processing circuit”, “processor”, and/or “processing unit” may be a single processing device or a plurality of processing devices. Such a processing device may be a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or operational instructions. The processing module, module, processing circuit, and/or processing unit may be, or further include, memory and/or an integrated memory element, which may be a single memory device, a plurality of memory devices, and/or embedded circuitry of another processing module, module, processing circuit, and/or processing unit. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that if the processing module, module, processing circuit, and/or processing unit includes more than one processing device, the processing devices may be centrally located (e.g., directly coupled together via a wired and/or wireless bus structure) or may be distributedly located (e.g., cloud computing via indirect coupling via a local area network and/or a wide area network). Further note that if the processing module, module, processing circuit, and/or processing unit implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory and/or memory element storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry. Still further note that, the memory element may store, and the processing module, module, processing circuit, and/or processing unit executes, hard coded and/or operational instructions corresponding to at least some of the steps and/or functions illustrated in one or more of the Figures. Such a memory device or memory element can be included in an article of manufacture.

One or more embodiments have been described above with the aid of method steps illustrating the performance of specified functions and relationships thereof. The boundaries and sequence of these functional building blocks and method steps have been arbitrarily defined herein for convenience of description. Alternate boundaries and sequences can be defined so long as the specified functions and relationships are appropriately performed. Any such alternate boundaries or sequences are thus within the scope and spirit of the claims. Further, the boundaries of these functional building blocks have been arbitrarily defined for convenience of description. Alternate boundaries could be defined as long as the certain significant functions are appropriately performed. Similarly, flow diagram blocks may also have been arbitrarily defined herein to illustrate certain significant functionality.

To the extent used, the flow diagram block boundaries and sequence could have been defined otherwise and still perform the certain significant functionality. Such alternate definitions of both functional building blocks and flow diagram blocks and sequences are thus within the scope and spirit of the claims. One of average skill in the art will also recognize that the functional building blocks, and other illustrative blocks, modules and components herein, can be implemented as illustrated or by discrete components, application specific integrated circuits, processors executing appropriate software and the like or any combination thereof.

In addition, a flow diagram may include a “start” and/or “continue” indication. The “start” and “continue” indications reflect that the steps presented can optionally be incorporated in or otherwise used in conjunction with other routines. In this context, “start” indicates the beginning of the first step presented and may be preceded by other activities not specifically shown. Further, the “continue” indication reflects that the steps presented may be performed multiple times and/or may be succeeded by other activities not specifically shown. Further, while a flow diagram indicates a particular ordering of steps, other orderings are likewise possible provided that the principles of causality are maintained.

The one or more embodiments are used herein to illustrate one or more aspects, one or more features, one or more concepts, and/or one or more examples. A physical embodiment of an apparatus, an article of manufacture, a machine, and/or of a process may include one or more of the aspects, features, concepts, examples, etc. described with reference to one or more of the embodiments discussed herein. Further, from figure to figure, the embodiments may incorporate the same or similarly named functions, steps, modules, etc. that may use the same or different reference numbers and, as such, the functions, steps, modules, etc. may be the same or similar functions, steps, modules, etc. or different ones.

Unless specifically stated to the contra, signals to, from, and/or between elements in a figure of any of the figures presented herein may be analog or digital, continuous time or discrete time, and single-ended or differential. For instance, if a signal path is shown as a single-ended path, it also represents a differential signal path. Similarly, if a signal path is shown as a differential path, it also represents a single-ended signal path. While one or more particular architectures are described herein, other architectures can likewise be implemented that use one or more data buses not expressly shown, direct connectivity between elements, and/or indirect coupling between other elements as recognized by one of average skill in the art.

The term “module” is used in the description of one or more of the embodiments. A module implements one or more functions via a device such as a processor or other processing device or other hardware that may include or operate in association with a memory that stores operational instructions. A module may operate independently and/or in conjunction with software and/or firmware. As also used herein, a module may contain one or more sub-modules, each of which may be one or more modules.

While particular combinations of various functions and features of the one or more embodiments have been expressly described herein, other combinations of these features and functions are likewise possible. The present disclosure is not limited by the particular examples disclosed herein and expressly incorporates these other combinations. 

What is claimed is:
 1. A method comprises: obtaining, by a first computing device of a computing network, a digital exchange item that is regarding at least one closed loop financial instrument; sending, by the first computing device to a server of the computing network, a request to share the digital exchange item with a group of computing devices that includes the first computing device; determining, by the server, whether the digital exchange item can be shared with the group of computing devices based on one or more of: an issuer agreement and exchange item rules; when the digital exchange item can be shared with the group of computing devices: establishing, by the server, secure custody rights for each computing device in the group of computing devices; determining, by the server, sharing rights regarding the digital exchange item; generating, by the server, replications of the digital exchange item; uploading, by the server, the replications of the digital exchange item and the sharing rights to digital wallets associated with other computing devices of the group of computing devices such that each computing device of the group of computing devices has access to the digital exchange item.
 2. The method of claim 1, wherein the obtaining comprises one of: purchasing, by the first computing device, the digital exchange item from a reselling computing device via the computing network; and purchasing, by the first computing device, the digital exchange item from an issuing server via the computing network, wherein the issuing server processed issuance of the digital exchange item.
 3. The method of claim 1, wherein the sending the request to share the digital exchange item further comprises: sending, as part of the request, a request to authenticate the group of computing devices; authenticating, by the server, each computing device of the group of computing devices; when each computing device of the group of computing devices has been authenticated: validating, by the server, that each computing device of the group of computing devices desires to be in the group of computing devices for sharing digital exchange items; and when each computing device of the group of computing devices desires to be in the group of computing devices, authenticating, by the server, the group of computing devices for sharing digital exchange items.
 4. The method of claim 1, wherein the determining whether the digital exchange item can be shared comprises: determining whether the group of computing devices is an authenticated sharing group; when the group of computing devices is an authenticated sharing group, determining whether the issuer agreement allows for exchange items to be shared; when the issuer agreement allows for exchange items to be shared, determining whether the exchange item rules allow for the digital exchange item to be shared; and when the exchange item rules allow for the digital exchange item to be shared, determining that the digital exchange item can be shared.
 5. The method of claim 1, wherein the establishing the secure custody rights for each computing device comprises: creating, by the server, a first secure data block regarding the first computing device obtaining the digital exchange item, wherein the first secure data block includes a first secure header section and a first secure transaction section, wherein the first secure header section includes encoded information regarding one or more previous transactions and wherein the first secure transaction section includes information regarding the first computing device obtaining the digital exchange item that is secured using an encryption key of the first computing device and is signed by the server; and creating, by the server, a second secure data block regarding a second computing device of the group of computing devices gaining group access to the digital exchange item, wherein the second secure data block includes a second secure header section and a second secure transaction section, wherein the second secure header section includes encoded information regarding the transaction in which the first computing device obtained the digital exchange item and wherein the second secure transaction section includes information regarding the second computing device having group access to the digital exchange item that is secured using an encryption key of the second computing device and is signed by the server.
 6. The method of claim 5 further comprises: creating, by the server, a third secure data block regarding a third computing device of the group of computing devices gaining group access to the digital exchange item, wherein the third secure data block includes a third secure header section and a third secure transaction section, wherein the third secure header section includes encoded information regarding the transaction in which the first computing device obtained the digital exchange item and the second computing device gained group access to the digital exchange item, and wherein the third secure transaction section includes information regarding the third computing device having group access to the digital exchange item that is secured using an encryption key of the third computing device and is signed by the server.
 7. The method of claim 1, wherein the sharing rights comprises one or more of: individual computing device use permissions; individual computing device use restrictions; individual computing device use conditions; group use permissions; group use conditions; and group use restrictions.
 8. The method of claim 1 further comprises: updating, by the server, an exchange item database to record that the digital exchange item is shared by the group of computing devices.
 9. A server for use in a computing network, the server comprises: an interface; memory; and a processing module operably coupled to the interface and the memory, wherein the processing module is operable to: receive, via the interface from a first computing device of the computing network, a request to share a digital exchange item with a group of computing devices that includes the first computing device, wherein the first computing device obtained the digital exchange item that is regarding at least one closed loop financial instrument; determine whether the digital exchange item can be shared with the group of computing devices based on one or more of: an issuer agreement and exchange item rules; when the digital exchange item can be shared with the group of computing devices: establish secure custody rights for each computing device in the group of computing devices; determine sharing rights regarding the digital exchange item; generate replications of the digital exchange item; upload, via the interface, the replications of the digital exchange item and the sharing rights to digital wallets associated with other computing devices of the group of computing devices such that each computing device of the group of computing devices has access to the digital exchange item.
 10. The server of claim 9, wherein the processing module is further operable to send the request to share the digital exchange item further by: sending, as part of the request, a request to authenticate the group of computing devices; authenticating each computing device of the group of computing devices; when each computing device of the group of computing devices has been authenticated: validating that each computing device of the group of computing devices desires to be in the group of computing devices for sharing digital exchange items; and when each computing device of the group of computing devices desires to be in the group of computing devices, authenticating the group of computing devices for sharing digital exchange items.
 11. The server of claim 9, wherein the processing module is further operable to determine whether the digital exchange item can be shared by: determining whether the group of computing devices is an authenticated sharing group; when the group of computing devices is an authenticated sharing group, determining whether the issuer agreement allows for exchange items to be shared; when the issuer agreement allows for exchange items to be shared, determining whether the exchange item rules allow for the digital exchange item to be shared; and when the exchange item rules allow for the digital exchange item to be shared, determining that the digital exchange item can be shared.
 12. The server of claim 9, wherein the processing module is further operable to establish the secure custody rights for each computing device by: creating a first secure data block regarding the first computing device obtaining the digital exchange item, wherein the first secure data block includes a first secure header section and a first secure transaction section, wherein the first secure header section includes encoded information regarding one or more previous transactions and wherein the first secure transaction section includes information regarding the first computing device obtaining the digital exchange item that is secured using an encryption key of the first computing device and is signed by the server; and creating a second secure data block regarding a second computing device of the group of computing devices gaining group access to the digital exchange item, wherein the second secure data block includes a second secure header section and a second secure transaction section, wherein the second secure header section includes encoded information regarding the transaction in which the first computing device obtained the digital exchange item and wherein the second secure transaction section includes information regarding the second computing device having group access to the digital exchange item that is secured using an encryption key of the second computing device and is signed by the server.
 13. The server of claim 12, wherein the processing module is further operable to: create a third secure data block regarding a third computing device of the group of computing devices gaining group access to the digital exchange item, wherein the third secure data block includes a third secure header section and a third secure transaction section, wherein the third secure header section includes encoded information regarding the transaction in which the first computing device obtained the digital exchange item and the second computing device gained group access to the digital exchange item, and wherein the third secure transaction section includes information regarding the third computing device having group access to the digital exchange item that is secured using an encryption key of the third computing device and is signed by the server.
 14. The server of claim 9, wherein the sharing rights comprises one or more of: individual computing device use permissions; individual computing device use restrictions; individual computing device use conditions; group use permissions; group use conditions; and group use restrictions.
 15. The server of claim 9, wherein the processing module is further operable to: update an exchange item database to record that the digital exchange item is shared by the group of computing devices.
 16. A computer readable storage device comprises: a first memory section that stores operational instructions that, when executed by a first computing device of a computing network, causes the first computing device to: obtain a digital exchange item that is regarding at least one closed loop financial instrument; and send, to a server of the computing network, a request to share the digital exchange item with a group of computing devices that includes the first computing device; a second memory section that stores operational instructions that, when executed by the server, causes the server to: determine whether the digital exchange item can be shared with the group of computing devices based on one or more of: an issuer agreement and exchange item rules; when the digital exchange item can be shared with the group of computing devices: establish secure custody rights for each computing device in the group of computing devices; determine sharing rights regarding the digital exchange item; generate replications of the digital exchange item; upload the replications of the digital exchange item and the sharing rights to digital wallets associated with other computing devices of the group of computing devices such that each computing device of the group of computing devices has access to the digital exchange item.
 17. The computer readable storage device of claim 16 further comprises: the first memory section further stores operational instructions that, when executed by the first computing device, causes the first computing device to send the request to share the digital exchange item by, sending, as part of the request, a request to authenticate the group of computing devices; and the second memory section further stores operational instructions that, when executed by the server, causes the server to: authenticate each computing device of the group of computing devices; when each computing device of the group of computing devices has been authenticated: validate that each computing device of the group of computing devices desires to be in the group of computing devices for sharing digital exchange items; and when each computing device of the group of computing devices desires to be in the group of computing devices, authenticate the group of computing devices for sharing digital exchange items.
 18. The computer readable storage device of claim 16, wherein the second memory section further stores operational instructions that, when executed by the server, causes the server to determine whether the digital exchange item can be shared by: determining whether the group of computing devices is an authenticated sharing group; when the group of computing devices is an authenticated sharing group, determining whether the issuer agreement allows for exchange items to be shared; when the issuer agreement allows for exchange items to be shared, determining whether the exchange item rules allow for the digital exchange item to be shared; and when the exchange item rules allow for the digital exchange item to be shared, determining that the digital exchange item can be shared.
 19. The computer readable storage device of claim 16, wherein the second memory section further stores operational instructions that, when executed by the server, causes the server to establish the secure custody rights for each computing device by: creating a first secure data block regarding the first computing device obtaining the digital exchange item, wherein the first secure data block includes a first secure header section and a first secure transaction section, wherein the first secure header section includes encoded information regarding one or more previous transactions and wherein the first secure transaction section includes information regarding the first computing device obtaining the digital exchange item that is secured using an encryption key of the first computing device and is signed by the server; and creating a second secure data block regarding a second computing device of the group of computing devices gaining group access to the digital exchange item, wherein the second secure data block includes a second secure header section and a second secure transaction section, wherein the second secure header section includes encoded information regarding the transaction in which the first computing device obtained the digital exchange item and wherein the second secure transaction section includes information regarding the second computing device having group access to the digital exchange item that is secured using an encryption key of the second computing device and is signed by the server.
 20. The computer readable storage device of claim 19, wherein the second memory section further stores operational instructions that, when executed by the server, causes the server to: creating a third secure data block regarding a third computing device of the group of computing devices gaining group access to the digital exchange item, wherein the third secure data block includes a third secure header section and a third secure transaction section, wherein the third secure header section includes encoded information regarding the transaction in which the first computing device obtained the digital exchange item and the second computing device gained group access to the digital exchange item, and wherein the third secure transaction section includes information regarding the third computing device having group access to the digital exchange item that is secured using an encryption key of the third computing device and is signed by the server.
 21. The computer readable storage device of claim 16, wherein the sharing rights comprises one or more of: individual computing device use permissions; individual computing device use restrictions; individual computing device use conditions; group use permissions; group use conditions; and group use restrictions.
 22. The computer readable storage device of claim 16, wherein the second memory section further stores operational instructions that, when executed by the server, causes the server to: update an exchange item database to record that the digital exchange item is shared by the group of computing devices. 